• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root I have the stock 4.1.2 Sprint rom for the ZTE Force 4G

For some reason zip was only 176mb instead of 248 so using DL manager on laptop with error checking. Should come out good.
 
SuperR said:
Both actually. Deodex cuts the size a bit, but most of the difference is the debloat
Click to expand...

Huh, I had gotten the impression from some other posts in other forums that deodex increased the file size and could make it slower.

Glad to know that it doesn't!

copying to SD now. About to flash.
 
sawbones999 said:
Huh, I had gotten the impression from some other posts in other forums that deodex increased the file size and could make it slower.

Glad to know that it doesn't!

copying to SD now. About to flash.
Click to expand...

Well, it does not make it slower. It makes the first boot slower, but no difference in speed after that
 
Formatting system...

Extracting system...

creating symlinks...

Setting Permissions...
E: Error in /sdcard/download/force_stock_4.1.2_deodexed.zip
(Status 7)
Installation aborted.

This is what I got. Gonna see if it will boot
 
I did a complete wipe. Data/factory reset, formatted system, dalvik, cache all first.

Downloading shinru's nandroid again. When I DL on phone I unzipped it and tried to restore and got md5 error.
 
ok, I took the files out of the folder which was named the same as the zip which were in the date coded folder of the nandroid which was nested in the zip named folder, moved them to the root of the zip named folder and deleted the date coded folder and it flashed.

Says restore complete. Gonna reboot now!
 
It said possibly lost root and asked to fix so I selected yes. Got a blank screen. Rebooted into recovery and trying fix permissions now
 
ok, rewiped. Restored again. Selected No when asked about fixing root....Still only got a black screen and it boot looped a couple times.

Once when it boot looped it played a sound? And the only thing that was lit up while booting was the home, back arrow, and menu at the bottom of the screen.

My hopes were so high!!!

Could the fact I am using an old CWM matter? I am using the 6.0.3.0 touch from the forum here.

Is there a way to get a full firmware dump and not just a nandroid? Does it not matter that there is no data.img in this nandroid?

Thanks,
-SB
 
I am about to leave so I can't troubleshoot with you, but after flashing the rom and getting the error, please go into the cwm log under advanced, and see what the error is. Thanks.
 
I got the same error as sawbones,
set_perm: some changes failes
E:Error in /tmp/update.zip
Status 7
Installation aborted.
Even with the CWM that you linked
 
Please get the cwm log and post what it says. Thanks. May not respond for a while.
 
Is it possible that this firmware requires a radio update or something?

Shinru, can you use dd to backup /modem? I think maybe you will find it at /dev/block/platform/msm_sdcc.1/by-name/modem judging from my cwm log.

Also you mentioned that you had the stock recovery that came on this phone? Can you post it?

What recovery are you using when you made the nandroid?

I wish sprint had made this available somewhere as an update package, or a full ROM.

Thanks,
-SB
 
This is the End of the log, If you need the whole thing, I'll gladly post it
Setting Permissions...set_perm: chown of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/left_eye-y0-yi45-p0-pi45-r0-ri20.2d_n2/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/left_eye-y0-yi45-p0-pi45-r0-ri20.2d_n2/full_model.bin to 644 failed: No such file or directory
script aborted: set_perm: some changes failed


set_perm: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
 
I was just reading through the recovery.log file from shinru's nandroid and noticed the LCD density is set to 320, while all updater scripts I have seen for the force 4g set it to 240. Could this cause a non boot issue?

Also I wonder if you (Shinru) could possibly download online nandroid backup from the play store and create a new nandroid for us from there? This program makes a nandroid while the system is up and will backup the modem to a modem.img, recovery to recovery.img, as well as system, data, cache, etc. And might give us a more complete backup to work from.

I updated to the cwm 6.0.4.4 from the forum and still got the same results flashing the nandroid from shinru and the zip from SuperR. Still the request to fix root.

Is it possible that this JB force has a different model # than n9100 or slightly modified hardware? Why else the change in pixel density?

Anyway, it would be awesome of you if you could make that more complete online nandroid so we can have the same modem img and recovery to test with.

Thanks so much for the help and effort! We've been waiting on this update for a long time and this seems to be our best shot at it do far!

Cheers,
-SB
 
TheFatDemon said:
This is the End of the log, If you need the whole thing, I'll gladly post it
Setting Permissions...set_perm: chown of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/left_eye-y0-yi45-p0-pi45-r0-ri20.2d_n2/full_model.bin to 0 0 failed: No such file or directory
set_perm: chmod of /system/vendor/pittpatt/models/detection/multi_pose_face_landmark_detectors.3/left_eye-y0-yi45-p0-pi45-r0-ri20.2d_n2/full_model.bin to 644 failed: No such file or directory
script aborted: set_perm: some changes failed


set_perm: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
Click to expand...

Thanks. I will fix this when I get home. May not get it posted till tomorrow.
 
Please try this one ;)
force_stock_4.1.2_deodexed_1b.zip

List of Removed Files:
/app/Books.apk
/app/ChromeWithBrowser.apk
/app/ConnectionsOptimizer.apk
/app/Exchange2.apk
/app/GMS_Maps.apk
/app/Hangouts.apk
/app/Magazines.apk
/app/Music2.apk
/app/PlusOne.apk
/app/SprintID.apk
/app/SprintZone.apk
/app/Swype.apk
/app/talkback.apk
/app/TouchPal.apk
/app/TwonkyMobile-release_ZTE.apk
/app/Videos.apk
/app/WiFiShare.apk
/app/WorldTime.apk
/app/YouTube.apk
/lib/libchromeview.so
/lib/libSwypeCore.so
/lib/libvideochat_jni.so
 
The Flash Process went without a hitch but it wont boot into any system. I see the initial boot one, the green android logo, and then the screen goes black. Its on because I see the white around the edges but after about a minute or so it just reboots. I even tried wiping the data and reflashing, nothing.

Edit: Btw, I'm still able to recover from nanodroid backup, if that matters.
 
TheFatDemon said:
The Flash Process went without a hitch but it wont boot into any system. I see the initial boot one, the green android logo, and then the screen goes black. Its on because I see the white around the edges but after about a minute or so it just reboots. I even tried wiping the data and reflashing, nothing.

Edit: Btw, I'm still able to recover from nanodroid backup, if that matters.
Click to expand...

I am not sure why it won't boot. Sounds like the same problem as the nandroid shinru2004 posted. No surprise there since it is the same system. Unfortunately, I don't have time to work on this for at least a week and I don't have a device to test on. At least you have a zip you can test with on your own if you want. You might want to swap the boot.img with stock 4.0.4 and see if that gets you booted. I kind of doubt it but it may be worth a try. The quantum rom booted in this manner and it was for different hardware so it may work.
 
SuperR said:
I am not sure why it won't boot. Sounds like the same problem as the nandroid shinru2004 posted. No surprise there since it is the same system. Unfortunately, I don't have time to work on this for at least a week and I don't have a device to test on. At least you have a zip you can test with on your own if you want. You might want to swap the boot.img with stock 4.0.4 and see if that gets you booted. I kind of doubt it but it may be worth a try. The quantum rom booted in this manner and it was for different hardware so it may work.
Click to expand...


What is the quantum ROM?

I PM'ed shinru and he said he will try making a nandroid with online nandroid backup so that we can get the modem.img and recovery.img along with everything else.

I'm hoping this might make a difference.

Cheers,
-SB
 
I have found more strangeness in the recovery.log for this ROM. the first thing I noticed is the LCD density, 320 instead of the usual 240.

Next is the build number. JLS36I. This is a build number for a CM10.2 ROM for the galaxy nexus. 320 is the standard LCD density for a galaxy nexus.

Then further down ro.cm.version=10.2-20132024-UNOFFICIAL-aurora

Then again ro.modversion=10.2-20132024-UNOFFICIAL-aurora

Next is galaxy4.apk which I googled and found out is the live wallpaper app found on the galaxy nexus.

It does however refer to the model number as n9100, and the make as ZTE, and aurora is the correct platform. Although it's listed as cm_aurora in at least one place.

The platform is correctly identified as msm8960.

So if this is an official Sprint Rom why does it seem to be based on a cyanogenmod 10.2 ROM from the galaxy nexus?

Also the ro.com.google.clientidbase in all four instances is = android-boost-us

Also ro.rommanager.developerid=cyanogenmod

Would Sprint really release a firmware based on CM10.2 for another platform or is there another way to interpret this info that I (being somewhat of a noob) am unaware of?

Is it possible that shinru's client got a used phone with someone's custom port of CM10.2 installed on it?

Very strange. Anyway I'm looking forward to your next nandroid for us shinru2004.

Thanks!
-SB
 
I did some more googling about the build number and did find other ROMs with it, but pretty much all were CM10.2....a few were aosp/cm10.2. Android version numbers all the way up to kit Kat.
 
You must log in or register to reply here.
Back
Top Bottom