As the titles states, I recently recovered my Nothing phone 1 from a fastboot loop after trying to go back to stock, locked bootloader from the latest android 13 PE rom.
I ended up somehow "seemingly" deleted all the partitions on the phone. While using most of THIS unbrick method. Although i supplied my own 1.1.4 full ROM, and matching super image.
I manually flashed all of the partitions for Slot A and they all completed with no issues.
I manually flashed all of them again on Slot B and got a few partition errors.
I set slot A as active and the phone booted up fine and booted into Nothing OS, However my finger print reader doesnt read my finger now and i cant boot slot B into recovery/fastbootd. it just reboots back into bootloader.
I found that i needed to flash the persist.img partition but ive done that and it still does the same thing, and i still cannot get Slot b into recovery/fastbootd.
I am both unlocked and Critical unlocked.
Verified that I used the correct global ROM and super.img for both 1.1.4 and 1.5.1
Ive tried re-doing everything, Flashing all the images before the super.img. After the super.img, the persist.img before and after as well.
Ive tried re-flashing everything but using the 1.5.1 Beta 2 hotfix, and matching boot.img and the same issue.
i tried re-flashing everything from the bootloader screen instead of fastbootd and same issue.
All my other sensors seem to work fine, including SIM Data, gyroscope, light sensors, camera flash, wifi. Everything except fingerprint.
Can anyone help me get this figured out? Ill try to answer any questions the best i can.
Thanks!
Tested all the sensors with a couple applications all of which aren't recognizing the fingerprint sensor as being in the phone at all.
Can anyone tell me when the persist image is supposed to be flash and possibly upload their persist image here so I can try it?
1.5.1 global version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey, did you by chance change the kernel?
Ofdas23 said:
Hey, did you by chance change the kernel?
Click to expand...
Click to collapse
Not as far as I know. At least not manually, unless they were part of one of the batch files that ran.
Decree said:
Not as far as I know. At least not manually, unless they were part of one of the batch files that ran.
Click to expand...
Click to collapse
Hmm, no, that's not the problem then
I don't know, flashing persist.img can have implications if not done properly and by no means am I any expert on this at all
I read that doing so improperly might end your device lose widevine L1 forever, which has impacts on DRM protected content, such as Netflix streams etc.
You could also try to recalibrate, I don't know the implications of that though, as it goes deeper into the system
I don't know if I would mess with that
Ofdas23 said:
You could also try to recalibrate, I don't know the implications of that though, as it goes deeper into the system
I don't know if I would mess with that
Click to expand...
Click to collapse
I have no clue how I would do that unfortunately
Decree said:
I have no clue how I would do that unfortunately
Click to expand...
Click to collapse
I think for that, you would have to be on stock ROM
also, how did you flash the images? In bootloader or fastbootd?
Fastbootd should be used
Edit:
Also I know, I am sending mixed signals, but when it comes to your slot b, maybe a recovery of a custom rom could fix it?
Ofdas23 said:
I think for that, you would have to be on stock ROM
also, how did you flash the images? In bootloader or fastbootd?
Fastbootd should be used
Edit:
Also I know, I am sending mixed signals, but when it comes to your slot b, maybe a recovery of a custom rom could fix it?
Click to expand...
Click to collapse
I am on stock 1.5.1 beta now
I flashed all images on slot a in fastbootd I tried to do that for slot B as well but I was unable to boot into it before. I would try to boot to recovery to do that and it would just loop back into bootloader.
Tonight, I flashed the PE room again per their instructions and then reflashed stock everything as if I was going back to stock with unlocked, and critical unlocked bootloader
Flashed boot and vendor boot for slot a, rebooted into fastbootd, flashed super.img, (which shows 25) then flashed all other images. Rebooted to bootloader and then flashed super again (this time it shows only 9) and then persist.
Did the same for slot B BUT this time I was actually able to boot to slot B recovery/fastbootd.
Phone boots up to stock Nothing OS again but still no working fingerprint.
Im honestly not sure if super should be flashed in fastbootd or bootloader or what order it should be flashed either. And the same for persist.Img
Decree said:
I am on stock 1.5.1 beta now
I flashed all images on slot a in fastbootd I tried to do that for slot B as well but I was unable to boot into it before. I would try to boot to recovery to do that and it would just loop back into bootloader.
Tonight, I flashed the PE room again per their instructions and then reflashed stock everything as if I was going back to stock with unlocked, and critical unlocked bootloader
Flashed boot and vendor boot for slot a, rebooted into fastbootd, flashed super.img, (which shows 25) then flashed all other images. Rebooted to bootloader and then flashed super again (this time it shows only 9) and then persist.
Did the same for slot B BUT this time I was actually able to boot to slot B recovery/fastbootd.
Phone boots up to stock Nothing OS again but still no working fingerprint.
Im honestly not sure if super should be flashed in fastbootd or bootloader or what order it should be flashed either. And the same for persist.Img
Click to expand...
Click to collapse
Hold on, is your persist.img a functional one? If so, then that will fix your fingerprint issue
Decree said:
I am on stock 1.5.1 beta now
I flashed all images on slot a in fastbootd I tried to do that for slot B as well but I was unable to boot into it before. I would try to boot to recovery to do that and it would just loop back into bootloader.
Tonight, I flashed the PE room again per their instructions and then reflashed stock everything as if I was going back to stock with unlocked, and critical unlocked bootloader
Flashed boot and vendor boot for slot a, rebooted into fastbootd, flashed super.img, (which shows 25) then flashed all other images. Rebooted to bootloader and then flashed super again (this time it shows only 9) and then persist.
Did the same for slot B BUT this time I was actually able to boot to slot B recovery/fastbootd.
Phone boots up to stock Nothing OS again but still no working fingerprint.
Im honestly not sure if super should be flashed in fastbootd or bootloader or what order it should be flashed either. And the same for persist.Img
Click to expand...
Click to collapse
Hold on, is your persist.img a functional one? If so, then that will fix your fingerprint issue
Als, could you please run this code in the phone dialer?
*#*#0#*#
Also, super is supposed to be flashed in fastboot, as far as I am concerned, no Guanajuato
Edit:
Also, do you have Telegram or something, for easier messaging?
Ofdas23 said:
Hold on, is your persist.img a functional one? If so, then that will fix your fingerprint issue
Hold on, is your persist.img a functional one? If so, then that will fix your fingerprint issue
Als, could you please run this code in the phone dialer?
*#*#0#*#
Also, super is supposed to be flashed in fastboot, as far as I am concerned, no Guanajuato
Edit:
Also, do you have Telegram or something, for easier messaging?
Click to expand...
Click to collapse
It should be. Although I found it posted in one of the threads I'll have to find. It's literally the only one I could find, I'm unsure of how to extract a working one from a ROM.
From what I read it stores the calibration for most of not all the sensors on the device, but literally ALL of mine work except the fingerprint.
I'll do the dialer thing in a couple minutes.
So in what order should someone be flashing the images?
Super, images, persist?
Or
Persist, super, images?
And everything should be flashed via fastbootd?
I Don't have telegram but Ill set one up!
Ofdas23 said:
Hold on, is your persist.img a functional one? If so, then that will fix your fingerprint issue
Click to expand...
Click to collapse
Here is the persist I've used. I did also flash this on 1.1.4 like the post says but now since slot B goes into fastboot I'll try it again tomorrow?
Post in thread 'How to unbrick Nothing Phone 1 fastboot bootloop' https://forum.xda-developers.com/t/...one-1-fastboot-bootloop.4501439/post-87527709
I also just made a telegram. Not sure what you need to add me or start a chat but my username is Anfurnyy
Decree said:
Here is the persist I've used. I did also flash this on 1.1.4 like the post says but now since slot B goes into fastboot I'll try it again tomorrow?
Post in thread 'How to unbrick Nothing Phone 1 fastboot bootloop' https://forum.xda-developers.com/t/...one-1-fastboot-bootloop.4501439/post-87527709
I also just made a telegram. Not sure what you need to add me or start a chat but my username is Anfurnyy
Click to expand...
Click to collapse
Use this app to restore it!
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
But use 1.1.4, as you said ^^
Ofdas23 said:
Use this app to restore it!
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
But use 1.1.4, as you said ^^
Click to expand...
Click to collapse
So you're saying use that app to put the persist. Img back into the file system and not flash it through fastboot?
Decree said:
So you're saying use that app to put the persist. Img back into the file system and not flash it through fastboot?
Click to expand...
Click to collapse
Yes, exactly, but it requires root!
Ofdas23 said:
Yes, exactly, but it requires root!
Click to expand...
Click to collapse
Shouldn't be a problem. Plenty of patched boots for 1.1.4 lol I'll give it a go tomorrow. Thanks for the idea!
Ofdas23 said:
Yes, exactly, but it requires root!
Click to expand...
Click to collapse
So I was able to get it back to 1.1.4 today with root, and restore the 1.1.4 persist.img from that post using that app and still doesn't work. Only thing left I can think of is try to extract one from another ROM file and after that try to send it back to Nothing.
Just wanted to add a bit of closure to this post. I ended up having to send the phone back to Nothing for an RMA and they just flat replaced it with a new device. There was no fix for the fingerprint sensor that they told me.
Of course, everything is up and working great now.
Related
UPDATE 10/02/2016- New version of TWRP has been released v3.0.3-0. See below:
https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html
I have updated versions SM-T800/805 with new builds. TWRP is now v3.0.3-1
TWRP OFFICIAL APP RELEASED: https://twrp.me/app/
Fixes:
Download mode now available in REBOOT options.
Root Shell now available in ADB.
Radio and Recovery backup.
System image backup/restore
Factory image flashing.
Supersu root option removed. This is to pre-empt the upgrade to MM which would cause a bootloop.
MTP fix - MTP now finally working in recovery.
Note: On my PC MTP works perfect in windows 7, but on Windows 8.1 was a little quirky. If you get a USB DEVICE NOT RECOGNISED error after enabling MTP, disable then quickly re-enable MTP and this should fix it.
This version also has system image backup and restore included. It is also possible to flash factory firmware images via the Image install button. (see the TWRP changelog above for more info)
UPDATE 5/3/16:
Have modified the twrp source code and extended factory image partition flashing to include all images except SBOOT.bin (still working on how to flash the bootloader via recovery)
This means BOOT, SYSTEM, RECOVERY, CACHE, HIDDEN, MODEM(RADIO) can all be flashed from the factory firmware. No need for ODIN anymore. As far as I know the Tab S is the only device supporting this at the moment.
(Note: to flash the modem it is necessary to rename MODEM.bin to MODEM.bin.img first)
TWRP_3.0.2-1-T700
TWRP-3.0.2-1-T705
TWRP-3.0.2-1-T800
NOTE: Certain models of the T800 version have a bug at the moment where the screen will be blank when booting to TWRP recovery until the screen timeout kicks in. After that pressing any button will show the screen. As a work around setting the timeout to 15 secs will shorten the wait.
TWRP-3.0.2-1-T805/T807(ATT or Verizon not supported)
twrp_3.0.3-1_sm-t800_10217
twrp_3.0.3-1_sm-t805_10217
FLASH WITH ODIN OR FLASHFIRE OR EXTRACT THE RECOVERY.IMG AND FLASH WITH TWRP
NOTE: It is important to boot to recovery after flashing with Odin or twrp may not stick and will be replaced with stock recovery.
When flashing uncheck auto reboot in Odin, immediately after flashing manually reboot and boot into twrp.
Manual reboot is POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FEEDBACK IS APPRECIATED PLEASE
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
gcappa said:
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
Click to expand...
Click to collapse
As long the bootloader is unlocked, and if someone has an stock recovery pulled from it, then he could be twrp for it
Bootloader is unlocked. But I already flashed a modified cwm which doesn't work too well. So not sure if I could pull the stock recovery unless I reflash the stock rom.
gcappa said:
Bootloader is unlocked. But I already flashed a modified cwm which doesn't work too well. So not sure if I could pull the stock recovery unless I reflash the stock rom.
Click to expand...
Click to collapse
If you have the firmware downloaded just right click on the md5 and open it with 7zip or Winrar, then simply just drag the recover IMG to your desktop and send it here(or link to download). I'm not going to go to much in depth as I don't want this thread to be filled with non related to twrp stuff. I'm also unsure if he has time but ash is one good recovery builder
Ok, I'll do all that when I get home and upload a link.
gcappa said:
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
Click to expand...
Click to collapse
Should be possible as long as the right files are available. This is a snapdragon 805 device?
Seeing as I don't have this device you would have to test the builds and I would need some info from the device. Might take a few builds to get a proper working one.
I take it you are currently rooted? Also could you send me a link to the version of cwm you are using?
gcappa said:
Ok, I'll do all that when I get home and upload a link.
Click to expand...
Click to collapse
Is the sm-n9100 the Chinese version Note 4 Duos?
The TWRP recovery below is for this version, please test:
twrp-2860-n1900
Stock Recovery:
Stock-recovery-n1900
Note: You take responsibility for testing this.
Failed to flash on my T-800.
dwarfer66 said:
Failed to flash on my T-800.
Click to expand...
Click to collapse
What failed to flash? It's made for the t800. It flashes fine on a t805. No one else has had any issues. What is the full version of your device?
ashyx said:
Unofficial version of the latest TWRP, don't think it's been released yet.
Found it by accident for another device, so have rebuilt it for the Tab S Exynos version only.
TWRP-2.8.6.1
Click to expand...
Click to collapse
Thank again ashy this is awesome, keep up the good work.
Confirmed its working T800 5.0.2
ashyx said:
What failed to flash? It's made for the t800. It flashes fine on a t805. No one else has had any issues. What is the full version of your device?
Click to expand...
Click to collapse
This unofficial TWRP fails to flash, just says failed when trying to install.
dwarfer66 said:
This unofficial TWRP fails to flash, just says failed when trying to install.
Click to expand...
Click to collapse
Again, you need to confirm what your exact model is and build number. As you can see from the post above it flashes fine on a T800.
Post a screenshot of the issue with Odin.
It's flashing for me ok on my T800 with IronRom 2.0. Only thing is the root ain't working. Or do I need to unselect auto-reboot and do a forced shutdown? And clear cache and reboot?
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
edit: reflashed IronRom 2.0 to fix cache issue. After the cache wipe it boots up
edit2: it appears to be rooted but it ain't working. But when an app should ask for root permissions the app goes black screen. For Titanium backup it just hangs on checking
RDDraco said:
It's flashing for me ok on my T800 with IronRom 2.0. Only thing is the root ain't working. Or do I need to unselect auto-reboot and do a forced shutdown? And clear cache and reboot?
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
edit: reflashed IronRom 2.0 to fix cache issue. After the cache wipe it boots up
edit2: it appears to be rooted but it ain't working. But when an app should ask for root permissions the app goes black screen. For Titanium backup it just hangs on checking
Click to expand...
Click to collapse
Did you update the supersu app as requested? You need to post a screenshot of root validator so I can see the status of root.
You may just need to select full unroot from settings in the supersu app then boot into twrp and run the root process again or flash the supersu2.46 zip.
Also regarding wiping cache, it can sometimes take longer depending on what's in cache at the time. It may seem like it's hung but eventually completes. On occasion I've seen it take up to a few minutes to wipe.
Just saying that root is broken on custom roms such as iron rom. It's an known issue with touchwiz lollipop roms.
-DUHA
So it's a Rom issue?
What's the actual problem?
Isn't the Rom already rooted, unusual for a custom Rom to not be prerooted?
Guess that explains why it wasn't working. (Tkkg1994 managed to get IronRom working with root in v2.0.5) so its fine for me now.
RDDraco said:
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
Click to expand...
Click to collapse
Looked into this issue and have fixed it. Wipe Cache should work now.
ashyx said:
Unofficial version of the latest TWRP, don't think it's been released yet.
Found it by accident for another device, so have rebuilt it for the Tab S Exynos version only.
TWRP-2.8.6.1
NOTE: If after using TWRP to root you don't see the notification to update Supersu, just install the latest Supersu app from Play. Check root status with Root Validator
Supersu
Root validator
Click to expand...
Click to collapse
Just today, I rooted my new Tab S (SM-T800) AFTER allowing it to OTA update to Android 5.0.2. After that, I used Odin to flash the latest version of CWM I could find for this device, and that trashed recovery altogether. Couldn't get into recovery at all. So I used Odin again to flash TWRP 2.8.6.0 and had recovery back, BUT I kept getting notifications that SuperSU needed to be updated. What I did then was flash "BETA-SuperSU-v2.48.zip", and that resolved the "update needed" problem, and all seems to be working smoothly now. :good:
I'm running stock Touchwiz Lollipop 5.0.2 . Haven't tried changing ROM's, but don't really have a desire to do that just yet.
UPDATE 12/3/2016 - All builds now posted in developer forum: http://forum.xda-developers.com/tab-s2/development/recovery-twrp-2-8-7-x-lollipop-5-1-1-t3205686
UPDATE 6/3/2016 - New version of TWRP has been released v3.0.0-0. See below:
https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
I have updated versions SM-T810 with a new build. TWRP is now v3.0.0-1
NOTE: This is a test build, I do not own this device. I need someone who knows what they are doing to test this out and report back.. A lot has changed in this version.
Features:
System image backup/restore
Factory image flashing.
F2FS support.
Supersu root option removed which would cause a bootloop on 5.1.1 and 6.0 devices.
MTP fix - MTP now finally working in recovery.
This version also has system image backup and restore included. It is also possible to flash factory firmware images via the Image install button. (see the TWRP changelog above for more info)
I have modified the twrp source code and extended factory image partition flashing to include all images except SBOOT.bin (still working on how to flash the bootloader via recovery)
This means BOOT, SYSTEM, RECOVERY, CACHE, HIDDEN, MODEM(RADIO) can all be flashed from the factory firmware. No need for ODIN anymore.
(Note: to flash the modem it is necessary to rename MODEM.bin to MODEM.bin.img first)
TWRP-3.0.0-1-T810
FLASH WITH ODIN OR FLASHFIRE OR EXTRACT THE RECOVERY.IMG AND FLASH WITH TWRP
NOTE: It is important to boot to recovery after flashing with Odin or twrp may not stick and will be replaced with stock recovery.
When flashing uncheck auto reboot in Odin, immediately after flashing manually reboot and boot into twrp.
Manual reboot is POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FEEDBACK IS APPRECIATED PLEASE
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Nice, are you planing on releasing TWRP 3 for T710? Would rly like to have Mount working.
mk89pwnz said:
Nice, are you planing on releasing TWRP 3 for T710? Would rly like to have Mount working.
Click to expand...
Click to collapse
I will, but nobody has confirmed if the t810 version is working yet. Looks like nobody wants the update.
ashyx said:
I will, but nobody has confirmed if the t810 version is working yet. Looks like nobody wants the update.
Click to expand...
Click to collapse
Not many active 810 users. Do u have 710 yourself? or non of these devices?
mk89pwnz said:
Not many active 810 users. Do u have 710 yourself? or non of these devices?
Click to expand...
Click to collapse
I build for loads of devices I don't own. I don't have the S2.
If you are willing to test I can make a T710 build.
As for the amount of T810 owners, there has been 55 downloads since posting this the other day and NOT ONE has bothered to provide feedback. :thumbdown:
ashyx said:
I build for loads of devices I don't own. I don't have the S2.
If you are willing to test I can make a T710 build.
As for the amount of T810 owners, there has been 55 downloads since posting this the other day and NOT ONE has bothered to provide feedback. :thumbdown:
Click to expand...
Click to collapse
I would definetly test it
Just tested it, tablet isn't booting anymore, it stucks on the samsung logo.
Neither in TWRP nor in system.
Reflashed your TWRP 2.8.7.1 and everything works again.
westernmg said:
Just tested it, tablet isn't booting anymore, it stucks on the samsung logo.
Neither in TWRP nor in system.
Reflashed your TWRP 2.8.7.1 and everything works again.
Click to expand...
Click to collapse
Can I ask which firmware build you are running? This build is using the latest kernel source BOJ1 which is a revision 2 firmware and may not be compatible with revision 1 bootloaders.
westernmg said:
Just tested it, tablet isn't booting anymore, it stucks on the samsung logo.
Neither in TWRP nor in system.
Reflashed your TWRP 2.8.7.1 and everything works again.
Click to expand...
Click to collapse
Can I ask which firmware build you are running? This build is using the latest kernel source BOJ1 which is a revision 2 firmware and may not be compatible with revision 1 bootloaders.
Please test this, it is built with the 5.1.1 kernel from the previous version: twrp_3.0.0-0_test2_t810
.
ashyx said:
I will, but nobody has confirmed if the t810 version is working yet. Looks like nobody wants the update.
Click to expand...
Click to collapse
??? http://forum.xda-developers.com/showpost.php?p=65197803&postcount=72
workdowg said:
??? http://forum.xda-developers.com/showpost.php?p=65197803&postcount=72
Click to expand...
Click to collapse
I changed a lot with this version, the build configuration itself is very different, kernel is built from latest source, modifications to the TWRP source code, mtp fix and hopefully even ADB working.
ashyx said:
I changed a lot with this version, the build configuration itself is very different, kernel is built from latest source, modifications to the TWRP source code, mtp fix and hopefully even ADB working.
Click to expand...
Click to collapse
Doesn't boot..
workdowg said:
Doesn't boot..
Click to expand...
Click to collapse
That's the test 2 version?
ashyx said:
That's the test 2 version?
Click to expand...
Click to collapse
The one from the OP is the only one I see....
workdowg said:
The one from the OP is the only one I see....
Click to expand...
Click to collapse
Post nr. 9
Flashing both from TWRP (using the image) and from Odin doesn't work, after restarting the recovery gets locked and unable to boot, as others wrote flashing the other TWRP from post 9 in your main TWRP thread works perfectly as far as booting, I did a couple of backups and worked fine, didn't restore the backups, so I can't tell you if restoring is fine.
Thanks for your efforts, I really appreciate them. :good:
kekinash said:
Flashing both from TWRP (using the image) and from Odin doesn't work, after restarting the recovery gets locked and unable to boot, as others wrote flashing the other TWRP from post 9 in your main TWRP thread works perfectly as far as booting, I did a couple of backups and worked fine, didn't restore the backups, so I can't tell you if restoring is fine.
Thanks for your efforts, I really appreciate them. :good:
Click to expand...
Click to collapse
Thanks, but you're confusing me, which version works? You say post #9, but that is this thread. :what:
I'm on LMY47X.T810XXU2BOJ1, the test2 is working so far.
But MTP doesn't seem to work for me.
On reboot to system it says "no OS installed ,are you sure to reboot?" but it boots fine....
ashyx said:
Can I ask which firmware build you are running? This build is using the latest kernel source BOJ1 which is a revision 2 firmware and may not be compatible with revision 1 bootloaders.
Please test this, it is built with the 5.1.1 kernel from the previous version: twrp_3.0.0-0_test2_t810
.
Click to expand...
Click to collapse
westernmg said:
I'm on LMY47X.T810XXU2BOJ1, the test2 is working so far.
But MTP doesn't seem to work for me.
On reboot to system it says "no OS installed ,are you sure to reboot?" but it boots fine....
Click to expand...
Click to collapse
It seems an issue with the kernel preventing boot to recovery with the earlier version. Not sure about the 'No OS installed' message, how can that be unless you wiped it?
Regarding MTP what actually happens?
Can you post the recovery.log on pastebin.com?
OK, it looks like TWRP is not able to mount anything.
The recovery.log cannot be written, also there is no access to the internal storage while trying to flash a zip or to restore a backup.
Got it on USB
ashyx said:
It seems an issue with the kernel preventing boot to recovery with the earlier version. Not sure about the 'No OS installed' message, how can that be unless you wiped it?
Regarding MTP what actually happens?
Can you post the recovery.log on pastebin.com?
Click to expand...
Click to collapse
Hey guys! Here is how to get recovery for your Z3 Compact without losing any files or flashing any kernels, as this could usually be a pain in the butt if you need a kernel for a custom rom...
I do not take credit for any of the resources in this guide and neither do i take any responsibility for bricked phones,dead SD cards or death
Click to expand...
Click to collapse
Prerequisites
1. Unlocked Bootloader (Its fairly easy to do, a simple google would suffice)
2. TWRP image- Get it Here
3. Flashtool installed with all required drivers
4. ADB and Fastboot (Here)
5. Patience
How to Install
1. Make sure you have an unlocked bootloader or this will, and shall not work.
2. Make sure you are running the latest firmware (.291). If not, use flashtool to update to the latest firmware.
3. Copy the downloaded TWRP image to your adb/fastboot folder and rename it recovery.img for ease.
4. Click shift+right click in any empty space in your adb/fastboot folder and click open command window here.
5. switch off your z3c. press the vol up button and insert USB cable to boot into fastboot mode
6. Make sure everything is working by typing
Code:
fastboot devices
in the cmd window. If all is well, then it should show your device's serial along with fastboot written beside it.
7. Time to flash the recovery:
Type in this command
Code:
fastboot flash recovery recovery.img
Congrats! You now have a recovery
8. To enter recovery mode, power off your phone, and press and hold Vol-down and Power button together until you see the sony logo.
You can now flash any rom or zips you want with this recovery, for root, flash the latest SuperSu Zip from chainfire.
I would also recommend flashing DRM fix zip.
If you want a better version of the stock rom, i will recommend installing SliMM Rom by Wajk
Note: This TWRP can get uninstalled in some cases, for example flashing a rom with twrp built in. But repeat the same process to get TWRP back without losing any data!
Thanks!
Hi, I'm from Brazil and I just bought a used D5833.
As usual, as soon as I bought the device, I did the procedure to unlock Bootloader without knowing that it was not necessary to get root and neither of the side effects of the unlock (about the quality of the camera and etc).
However the whole procedure worked well to install RECOVERY but I still could not get root.
I am using a MM 6.0.1 and TWRP 3.0.2-1 and the problem is always the same at the time of doing the FLASH in Supersu:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
I tried with the following versions of SUPERSU:
UPDATE-SuperSU-v2.65-20151226141550.zip
BETA-SuperSU-v2.68-20160228150503.zip
UPDATE-SuperSU-v2.76-20160630161323.zip
SR4-SuperSU-v2.78-SR4-20161115184928.zip
Older versions cause a bootloop
I keep looking but I can not do ROOT
I would even like to install the SliMM ROM but you need root first.
Could you help me ??
dansan691 said:
Hi, I'm from Brazil and I just bought a used D5833.
As usual, as soon as I bought the device, I did the procedure to unlock Bootloader without knowing that it was not necessary to get root and neither of the side effects of the unlock (about the quality of the camera and etc).
However the whole procedure worked well to install RECOVERY but I still could not get root.
I am using a MM 6.0.1 and TWRP 3.0.2-1 and the problem is always the same at the time of doing the FLASH in Supersu:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
I tried with the following versions of SUPERSU:
UPDATE-SuperSU-v2.65-20151226141550.zip
BETA-SuperSU-v2.68-20160228150503.zip
UPDATE-SuperSU-v2.76-20160630161323.zip
SR4-SuperSU-v2.78-SR4-20161115184928.zip
Older versions cause a bootloop
I keep looking but I can not do ROOT
I would even like to install the SliMM ROM but you need root first.
Could you help me ??
Click to expand...
Click to collapse
No, you can install SliMM directly. To get root, you should be using armv23 version... Try this. Also, you should use a DRM restore zip to get back camera quality
Clarification
Should I have to flash DRM Fix every time I flash TWRP?
andry360 said:
Should I have to flash DRM Fix every time I flash TWRP?
Click to expand...
Click to collapse
No need. But if you change reflash ROM, you might need to
i was able to flash to recovery but ive tried tons of version of supersu but still cant get root access, can you give a step by step instructions on how to? thank you so much.
epiii_nephrine said:
i was able to flash to recovery but ive tried tons of version of supersu but still cant get root access, can you give a step by step instructions on how to? thank you so much.
Click to expand...
Click to collapse
Can you please give me the error you get?
panzerox123 said:
Can you please give me the error you get?
Click to expand...
Click to collapse
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
ive tried almost all versions of supersu.
im running the latest stockfirware.
i hope you could help, i really need to get root access on my d5833. thanks
epiii_nephrine said:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
ive tried almost all versions of supersu.
im running the latest stockfirware.
i hope you could help, i really need to get root access on my d5833. thanks
Click to expand...
Click to collapse
Alright... I know what's up. If you can wait till 9PM IST today, I will create another guide. Thanks!
To Get Root
As I can see, many people are having trouble getting root on their devices. You cannot directly get root on .291 as far as I know.
But since I do not use the stock firmware, there is no way for me to test. I will be using you people as testers now. I know of two methods. First , the shorter one. I got the supersu from Xperience ROM.
Please try this and let me know. Otherwise, the other method is pretty hard and requires flashing kernels.
Download the file from the attachment down.
@epiii_nephrine
panzerox123 said:
As I can see, many people are having trouble getting root on their devices. You cannot directly get root on .291 as far as I know.
But since I do not use the stock firmware, there is no way for me to test. I will be using you people as testers now. I know of two methods. First , the shorter one. I got the supersu from Xperience ROM.
Please try this and let me know. Otherwise, the other method is pretty hard and requires flashing kernels.
Download the file from the attachment down.
@epiii_nephrine
Click to expand...
Click to collapse
Thank you so much sir! will be testing this version.. i'll let you know :good:
epiii_nephrine said:
Thank you so much sir! will be testing this version.. i'll let you know :good:
Click to expand...
Click to collapse
Sure! If this does not work, I have another method.
After installing the recovery. Every time i reboot my mobile. It goes to TWRP directly.
smahio said:
After installing the recovery. Every time i reboot my mobile. It goes to TWRP directly.
Click to expand...
Click to collapse
Doesn't make any sense... It would so that only if you flashed to boot partition. Download EliteKernel V3 , extract the zip, keep the boot.img in your minimal adb folder and do
Fastboot flash boot boot.img
Then try again
I am having issue with TWRP 3.0.2-1 on my D5833. 3.0.2-0 and other previous versions ran without problem on my Z3C but the display problem occurred in TWRP 3.0.2-1 and the situation is similar with the photo below. (It was running an AOSP 7.1 ROM for Z3C D5803, the bottom of the screen could not display correctly, and the entire screen was flashing)
According to my observations, when my D5833 was running TWRP 3.0.2-1, the color temperature of the interface was colder than that of 3.0.2-0, I guess that's due to a change in the graphics mode or something similar, and once I set the color temperature to warmer (i.e. change the display mode), it will display everything correctly. However, I just can't figure out how to do that, maybe editing some codes? Can anyone please help me?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ewjy said:
I am having issue with TWRP 3.0.2-1 on my D5833. 3.0.2-0 and other previous versions ran without problem on my Z3C but the display problem occurred in TWRP 3.0.2-1 and the situation is similar with the photo below. (It was running an AOSP 7.1 ROM for Z3C D5803, the bottom of the screen could not display correctly, and the entire screen was flashing)
According to my observations, when my D5833 was running TWRP 3.0.2-1, the color temperature of the interface was colder than that of 3.0.2-0, I guess that's due to a change in the graphics mode or something similar, and once I set the color temperature to warmer (i.e. change the display mode), it will display everything correctly. However, I just can't figure out how to do that, maybe editing some codes? Can anyone please help me?
Click to expand...
Click to collapse
Sh*t this is bad. I dont think it has anything to do with twrp. Try reinstalling stock android marshmallow.
If that doesnt work, than it is a definite problem with hardware.
panzerox123 said:
Sh*t this is bad. I dont think it has anything to do with twrp. Try reinstalling stock android marshmallow.
If that doesnt work, than it is a definite problem with hardware.
Click to expand...
Click to collapse
Thanks for the reply. I have tried to reinstall the stock ROM and many other methods but no one would fix the display problem of TWRP 3.0.2-1 and most third-party ROMs. There are only three types of ROMs can run without display problems on my D5833: stock Sony Xperia ROM, official CyanogenMod 12.1 builds and any third-party ROMs mainly based on stock Xperia ROM and / or CM. CM builds higher than 12.1 will occur the display problems too.
I remember there is another characteristic: the boot screen can indicate the situation - when the boot screen shows "SONY" logo at the center with "XPERIA" logo at the bottom, there is NO display problem. When the boot screen only shows "SONY" logo and the bottom is empty, there WILL BE display problem. It's quite weird.
ewjy said:
Thanks for the reply. I have tried to reinstall the stock ROM and many other methods but no one would fix the display problem of TWRP 3.0.2-1 and most third-party ROMs. There are only three types of ROMs can run without display problems on my D5833: stock Sony Xperia ROM, official CyanogenMod 12.1 builds and any third-party ROMs mainly based on stock Xperia ROM and / or CM. CM builds higher than 12.1 will occur the display problems too.
I remember there is another characteristic: the boot screen can indicate the situation - when the boot screen shows "SONY" logo at the center with "XPERIA" logo at the bottom, there is NO display problem. When the boot screen only shows "SONY" logo and the bottom is empty, there WILL BE display problem. It's quite weird.
Click to expand...
Click to collapse
oh OK. If this problem did not exist on older version of TWRP, then using the same method, roll back to twrp 3.0.2-0. you just need to download that file. All the best!
panzerox123 said:
oh OK. If this problem did not exist on older version of TWRP, then using the same method, roll back to twrp 3.0.2-0. you just need to download that file. All the best!
Click to expand...
Click to collapse
Indeed there will be no problem for older versions. However, I am still unable to install and run many third-party ROMs smoothly, that means the number of ROMs I can try out is limited. Anyway, that is alright, thanks for your reply.
ewjy said:
Indeed there will be no problem for older versions. However, I am still unable to install and run many third-party ROMs smoothly, that means the number of ROMs I can try out is limited. Anyway, that is alright, thanks for your reply.
Click to expand...
Click to collapse
Funny... It works very well for me... In fact it's much more stable than previous versions
Bootloader is open but TWRP is giving ERROR1 when trying to flash Root, and also is unable to mount any partition...
Any help from someone who managed?
***Important Update!*** I am almost sure the problem is with Huawei shipping the P10/P10Plus with different storage chips.
Myself unfortunately got the eMMC chip + LPDDR4 memory. This is why TWRP is unable to mount any partition since the .fstab is different.
I have a working TWRP I ported myself which I was able to rebrand with, root yet to be confirmed. If you need it PM me.
I strongly advise anyone trying to flash TWRP to check their storage chip first using adb command "ls /proc/fs/*".
If you get mmcblk your F******, SD or UFS you are good.
I have an AL00 (rebranded to L29) that I rooted without too much hassle. The key is NOT sliding the first screen in TWRP. You have to click the read only button and then flash the phh nocrypt root zip.
Thanks!
Goronok said:
I have an AL00 (rebranded to L29) that I rooted without too much hassle. The key is NOT sliding the first screen in TWRP. You have to click the read only button and then flash the phh nocrypt root zip.
Click to expand...
Click to collapse
I would kindly appreciate links used and a short walkthrough...sent you a PM.
Thank you so much!
MosquitoByte said:
I would kindly appreciate links used and a short walkthrough...sent you a PM.
Thank you so much!
Click to expand...
Click to collapse
https://www.gizdev.com/root-huawei-p10-p10-plus-install-twrp/
If you follow this guide exactly, you'll be rooted without issues. (you can use their files, they work fine) Two things to watch for :
1. You absolutely cannot slide the first slider in TWRP to allow modifications. You have to click the read only button.
2. It will only work on a fresh install / fresh boot.img. If you've already allowed modifications within TWRP, you're stuck. You have to flash a new boot.img or completely re-install EMUI via update.zip or funkyhuawei.
Hope this helps
Thanks so much for your Info Goronok.
I got the same problem.. No possibility of a full root and system partition is write protected..
One question:
Is ist possible to do a factory reset out of the settings as well?
Or do we have to go for the funkyhuawei method?
How can i update.zip the system if its not possible to make a dload folder in the root folder on system partition?
Can someone uplad the boot.img for VKY-L09C432B130, if that will save the problem too... ?
Ok that wasnt one, that were 4 questions.. but thanks so much in advance
Kind Regards
Dennis
DV87XDA said:
Thanks so much for your Info Goronok.
I got the same problem.. No possibility of a full root and system partition is write protected..
One question:
Is ist possible to do a factory reset out of the settings as well?
Or do we have to go for the funkyhuawei method?
How can i update.zip the system if its not possible to make a dload folder in the root folder on system partition?
Can someone uplad the boot.img for VKY-L09C432B130, if that will save the problem too... ?
Ok that wasnt one, that were 4 questions.. but thanks so much in advance
Kind Regards
Dennis
Click to expand...
Click to collapse
1. No factory reset within the device will help you once you've swiped to allow modifications within TWRP.
2. I did funkyhuawei, so it's the only thing I can speak to. This method will absolutely work assuming you dont mind spending a few dollars and have a router where you can specify DNS.
3. update.zip should (in theory) work from sdcard, though I have not personally tried it. I think most of the people mentioning this method are coming from a P9/Mate9, which does things a little differently.
4. I have not seen a link for VKY-B130 yet, but here is one for B124. The boot.img here should work just the same... http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1475/g104/v82453/f2/full/update.zip
can't figure out what is wrong
First time I tried to root I did slide the "allow modifications"...
I reinstalled stock twice with FunkyHuawei but still can't get TWRP to work.
It seems it doesn't have access to any partition.
Phone boots normally though...
Any ideas?
Please.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://imgur.com/a/nzog4
Hey Mosquito, i guess we both have the same kinda Problem.
I will do the following steps today and let you guys know, if and how it worked out.
The only problem is, im not at home right now, so i dont have access to a router where i can change the DNS. So no FunkyHuawei method for me.
I will do the following steps today:
1. Donwloading the VKY-L09C432B130 jus now. Trying to flash the original boot.img and do the TWRP and root again, WITHOUT swping the TWRP allow modifications slider
2. If No 1 doesnt work i will copy the download update.app, will create a dload folder on my external sd card and copy update.app in it. Then trzing to freshly install the downloaded firmware.
3. If there is somehow a failure or any error with the automated update i will factory reset the phone via settings and then see whtats going on.
I hope everything will work out fine, even without the possibility of FunkyHuawei Reset.
Keep in mind that there are two types of TWRP online available for the P10Plus Version 3.0.2.2 and version 3.1.0.0.. maybe the root works different with the different TWRPs. At this moment im not quite sure which one i use.. probably the one from gizdev, what Goronok told us to use.
I keep you up to date whats going on!
Thanks guys
Regards
Dennis
Been there..
DV87XDA said:
Hey Mosquito, i guess we both have the same kinda Problem.
I will do the following steps today and let you guys know, if and how it worked out.
The only problem is, im not at home right now, so i dont have access to a router where i can change the DNS. So no FunkyHuawei method for me.
I will do the following steps today:
1. Donwloading the VKY-L09C432B130 jus now. Trying to flash the original boot.img and do the TWRP and root again, WITHOUT swping the TWRP allow modifications slider
2. If No 1 doesnt work i will copy the download update.app, will create a dload folder on my external sd card and copy update.app in it. Then trzing to freshly install the downloaded firmware.
3. If there is somehow a failure or any error with the automated update i will factory reset the phone via settings and then see whtats going on.
I hope everything will work out fine, even without the possibility of FunkyHuawei Reset.
Keep in mind that there are two types of TWRP online available for the P10Plus Version 3.0.2.2 and version 3.1.0.0.. maybe the root works different with the different TWRPs. At this moment im not quite sure which one i use.. probably the one from gizdev, what Goronok told us to use.
I keep you up to date whats going on!
Thanks guys
Regards
Dennis
Click to expand...
Click to collapse
I already did everything you wrote, still no go.
Please update me if you get a different result.
Tried both TWRP versions.
What firmware you had at first?
I have bought my phone 10 days ago.
From T-Mobile Germany.
VKY-L09 6GB Version, Single Sim i guess.
Not sure what Firmware i had when i bought it, cause I immediately tried to root after buying, without checking the FW Version.
But I did a FunkyHuawei Restore before with VKY-L09C432B130 Firmware and it worked.
Only the Full Root is the Problem right now.. damnit.
I Will try everything and let you know.
Later!
MosquitoByte said:
First time I tried to root I did slide the "allow modifications"...
I reinstalled stock twice with FunkyHuawei but still can't get TWRP to work.
It seems it doesn't have access to any partition.
Phone boots normally though...
Any ideas?
Please.....
http://imgur.com/a/nzog4
Click to expand...
Click to collapse
What root zip are you trying to flash?
That from gizdev. Superroot.noverity.nocrypt.zip
Hey Guys i made it ! Yesss Thats awesome !
Im doing a Factory Reset now for a clean install of everything. Just because i want a fresh and new phone
Mosquito what Firmware are you on?
Let me know your Firmware Number and i explain what to do..
Ohhh Great
DV87XDA said:
Hey Guys i made it ! Yesss Thats awesome !
Im doing a Factory Reset now for a clean install of everything. Just because i want a fresh and new phone
Mosquito what Firmware are you on?
Let me know your Firmware Number and i explain what to do..
Click to expand...
Click to collapse
I am now reverting to VKY-AL00C00B123 using FunkyHuawei...Please share what to do next
Ok forget my last post.. sorry!
Here is what to do:
Whoever gets the Error 1 Message when installing the SuperRoot_noverity_nocrypt zip, do the follwoing:
Get your Firmware Number, download the whole Firmware (about 2GB +/-) and download the huaweiextractor from here
https://forum.xda-developers.com/showthread.php?t=2433454
Start the Huaweiextractor exe and unpack the boot.img.
Start your phone into bootloader
Flash boot.img (of your original firmware, the one u unpacked just now) to your phone via fastboot flash boot bot.img
Then start your TWRP Recovery
Clear Cache/Dalvik
then install the SuperRoot_noverity_nocrypt, this time you wont get a error
then wipe cache/Dalvik
reboot
enjoy our FUll root on Your P10plus or P10
Best regards
Dennis
DV87XDA said:
Ok forget my last post.. sorry!
Here is what to do:
Whoever gets the Error 1 Message when installing the SuperRoot_noverity_nocrypt zip, do the follwoing:
Get your Firmware Number, download the whole Firmware (about 2GB +/-) and download the huaweiextractor from here
https://forum.xda-developers.com/showthread.php?t=2433454
Start the Huaweiextractor exe and unpack the boot.img.
Start your phone into bootloader
Flash boot.img (of your original firmware, the one u unpacked just now) to your phone via fastboot flash boot bot.img
Then start your TWRP Recovery
Clear Cache/Dalvik
then install the SuperRoot_noverity_nocrypt, this time you wont get a error
then wipe cache/Dalvik
reboot
enjoy our FUll root on Your P10plus or P10
Best regards
Dennis
Click to expand...
Click to collapse
I think I tried that already,
I will try again..
Where did you get your firmware from and what firmware you were on?
I have the Firmware L09C432B130 and i downloaded from here:
http://www.stechguide.com/download-huawei-p10-plus-nougat-firmware-update/
Just google your firmware and downloaded.
You need the exact 100% same boot.img from your installed firmware.
Then it will work for sure!
DV87XDA said:
I have the Firmware L09C432B130 and i downloaded from here:
http://www.stechguide.com/download-huawei-p10-plus-nougat-firmware-update/
Just google your firmware and downloaded.
You need the exact 100% same boot.img from your installed firmware.
Then it will work for sure!
Click to expand...
Click to collapse
Dennis,
Can you please check for me if TWRP mounts partitions correctly for you?
I suspect the problem for me is incompatibility of the available TWRP with the Chinese version, or some sort of data encryption embedded.
MosquitoByte said:
Dennis,
Can you please check for me if TWRP mounts partitions correctly for you?
I suspect the problem for me is incompatibility of the available TWRP with the Chinese version, or some sort of data encryption embedded.
Click to expand...
Click to collapse
Is your device an AL00?
Goronok said:
Is your device an AL00?
Click to expand...
Click to collapse
Yes indeed.
Hi, I created this thread because I have solved the problem of the 4g at the time of losing my "moto g5 imei".
Just installed the "dotos rom v2. 2" 06/05/2018, I went into the bootloader, did the respective backup (currently at H +), and entered modem commands in fastboot mode, all this with the 64 twrp, say because I have read that he has to go to twrp's 32 " , but no, I didn't do it, well, at the time of start the rom again because you will have 4 g, well that was my case, I don't know if it will work with some of you, perhaps to serve them, my specific model is the xt1670.
Anyway here are the steps:
1 -- Get a backup of the file "EFS" (currently with H +), to me only appears me with the 64-bit TWRP '
2 -- Install the rom "dotOS v2.2 - 20180506 ", if you don't have any rom with android 8.1, install first the TWRP 64 and then the rom "dotos".
3 -- Once installed restart mobile to bootloader, and do not change anything.
4 -- Just enter via adb fastboot commands:
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
5 -- Will restart automatically, and you will already have the 4 g network.
6 -- Finally performs a backup of the file "EFS" 4g.
POSSIBLE PROBLEM...
Lack say something, possibly the "imei sv" is set to 0, the solution for me was after having keep the new file efs with 4 g, I installed the "moto g5 official rom (android 7.0)", with full commands, including modems, obviously we will lose the imei, but because we have our file efs 4g, we will restore it, we go back to bootloader mode, install again the 64 twrp, we also install the file "no verity opt encrypt 6.0", then, we return to the main menu of the twrp and restore, and choose the file that we have recovered the EFS 4 g, and " ready, we have a imei, imei sv, and 4 g correctly, upon restart, if you like you make another backup of the definitive efs file, and ready, now if you want to go back to the stock rom, already not to enter modem commands, thats all.
PD: Sorry for my english, I used a translator for this... And sorry for the links, xda will not allow me...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How i get backup of EFS file ?
Thanks for the tutorial, it has served me many gracais since I was 4 months in 3g. just follow the letter
Kindred403 said:
How i get backup of EFS file ?
Click to expand...
Click to collapse
Sorry for the delay in responding, you can only get the EFS file from the recovery Cedric TWRP 64 bits, that is very important, and being in the Backup menu, select the EFS file.
Finally my 4G is back! Thank you very much!
If I update after doing this, will I lose IMEI and have to flash stock again?
ap4ss3rby said:
If I update after doing this, will I lose IMEI and have to flash stock again?
Click to expand...
Click to collapse
No, not at all, just ignore the modem commands, and if you mean to install custom ROMs, will go normal, no errors
sashUser_2 said:
Hi, I created this thread because I have solved the problem of the 4g at the time of losing my "moto g5 imei".
Just installed the "dotos rom v2. 2" 06/05/2018, I went into the bootloader, did the respective backup (currently at H +), and entered modem commands in fastboot mode, all this with the 64 twrp, say because I have read that he has to go to twrp's 32 " , but no, I didn't do it, well, at the time of start the rom again because you will have 4 g, well that was my case, I don't know if it will work with some of you, perhaps to serve them, my specific model is the xt1670.
Anyway here are the steps:
1 -- Get a backup of the file "EFS" (currently with H +), to me only appears me with the 64-bit TWRP '
2 -- Install the rom "dotOS v2.2 - 20180506 ", if you don't have any rom with android 8.1, install first the TWRP 64 and then the rom "dotos".
3 -- Once installed restart mobile to bootloader, and do not change anything.
4 -- Just enter via adb fastboot commands:
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
5 -- Will restart automatically, and you will already have the 4 g network.
6 -- Finally performs a backup of the file "EFS" 4g.
POSSIBLE PROBLEM...
Lack say something, possibly the "imei sv" is set to 0, the solution for me was after having keep the new file efs with 4 g, I installed the "moto g5 official rom (android 7.0)", with full commands, including modems, obviously we will lose the imei, but because we have our file efs 4g, we will restore it, we go back to bootloader mode, install again the 64 twrp, we also install the file "no verity opt encrypt 6.0", then, we return to the main menu of the twrp and restore, and choose the file that we have recovered the EFS 4 g, and " ready, we have a imei, imei sv, and 4 g correctly, upon restart, if you like you make another backup of the definitive efs file, and ready, now if you want to go back to the stock rom, already not to enter modem commands, thats all.
PD: Sorry for my english, I used a translator for this... And sorry for the links, xda will not allow me...
Click to expand...
Click to collapse
Please make a video of it ?
I don't know why you keep saying you have to install dotos to do this? Worked on atomic os.
After doing the fastboot commands the IMEI went to 0 but then after restore the EFS it came back to normal....
I can't say if 4g is back because where I am I had never got 4g before.. I'll have to travel somewhere to see if 4g is back!
Seems possible that 4g is back now! Thanks! ?
Sadly this didn't fix my 4g not working issue ?
This worked perfectly, and I was just thinking about buying another phone. Thanks a lot!
where do we have to take backup of efs. stock rom or dotOS rom ??
Varun Maheshwari said:
where do we have to take backup of efs. stock rom or dotOS rom ??
Click to expand...
Click to collapse
First things first, you gotta be sure you are on stock rom AND have 3G signal. If you don't, flash the latest Pixel Experience so you get IMEI and 3G back (may need to reboot phone twice, I did). After that, you have to flash back stock rom via fastboot mode so make sure you enabled USB debugging (I'm assuming you already know that), but don't run the commands 'fastboot erase modemst1' and 'fastboot erase modemst2'. If you run these, you'll have to start all over. Once you're all set, backup EFS partition using TWRP 3.2.1-0 (64bit version linked above), save it somewhere safe, install dotOS rom (I used the exact version the tutorial suggests, so I would just stick with that), reboot to system (again, you may have to reboot it twice) and you should have 4G/LTE signal. Now create a new EFS backup, save it somewhere safe, and reinstall stock ROM, but this time including those two commands (I installed the latest version with July 2018 security patch). After that, reinstall TWRP 64bits, restore the EFS backup you created while on dotOS and you're done. On First boot you may face some problems while trying to use 4G, it may keep switching between 4G and 3G all the time making it impossible to connect, but should it happen to you, a simple reboot fixes the issue. If you wish to root your phone after the process (like I did for PoGO spoofing) just install 32bit TWRP 3.2.2-0 and flash Magisk 16.7 beta and reboot phone twice (First time may have 4G issue again, rebooting fixes it). Sorry for the late response, it's way past midnight here in Brazil. Hope you get It working again
I finally got my 4g back after a long time thanks brother!!!!
patricksouza472 said:
First things first, you gotta be sure you are on stock rom AND have 3G signal. If you don't, flash the latest Pixel Experience so you get IMEI and 3G back (may need to reboot phone twice, I did). After that, you have to flash back stock rom via fastboot mode so make sure you enabled USB debugging (I'm assuming you already know that), but don't run the commands 'fastboot erase modemst1' and 'fastboot erase modemst2'. If you run these, you'll have to start all over. Once you're all set, backup EFS partition using TWRP 3.2.1-0 (64bit version linked above), save it somewhere safe, install dotOS rom (I used the exact version the tutorial suggests, so I would just stick with that), reboot to system (again, you may have to reboot it twice) and you should have 4G/LTE signal. Now create a new EFS backup, save it somewhere safe, and reinstall stock ROM, but this time including those two commands (I installed the latest version with July 2018 security patch). After that, reinstall TWRP 64bits, restore the EFS backup you created while on dotOS and you're done. On First boot you may face some problems while trying to use 4G, it may keep switching between 4G and 3G all the time making it impossible to connect, but should it happen to you, a simple reboot fixes the issue. If you wish to root your phone after the process (like I did for PoGO spoofing) just install 32bit TWRP 3.2.2-0 and flash Magisk 16.7 beta and reboot phone twice (First time may have 4G issue again, rebooting fixes it). Sorry for the late response, it's way past midnight here in Brazil. Hope you get It working again
Click to expand...
Click to collapse
thankyou so much..it worked
Guys I can not get 4g back at all, I run the command fastboot erase modemst1
fastboot erase modemst2 on pixel rom as I only have 3G andnd this wiped my IMEI and put it to 0, so then I had to reinstall stock oreo rom with all the commands (not erase modemst etc) then wipe then install pixel rom to get 3g back, I can't get 4g how do I do it it's driving my crazy!
please help
Any update? I really need 4G working again, the erase modemst1/2 commands just wiped my IMEI on this guide, then I had to start all over again just to get 3G working and my IMEI back again.
junglebungle said:
Any update? I really need 4G working again, the erase modemst1/2 commands just wiped my IMEI on this guide, then I had to start all over again just to get 3G working and my IMEI back again.
Click to expand...
Click to collapse
Have a look at this guide. It is for Potter, but the same principles apply to Cedric
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
NZedPred said:
Have a look at this guide. It is for Potter, but the same principles apply to Cedric
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
Click to expand...
Click to collapse
Wow that looks very difficult, I don't want to mess up my phone even more
I mean I have IMEI and 3G, I just need my 4G back..
junglebungle said:
Wow that looks very difficult, I don't want to mess up my phone even more
I mean I have IMEI and 3G, I just need my 4G back..
Click to expand...
Click to collapse
Quite often 4G is missing for the same reason. What rom are you on right now? If you are on stock nougat, then flash this zip
https://androidfilehost.com/?fid=3700668719832240875
All this zip does is fix the ownership of a couple of folders in the persist partition. If this is the issue you're facing (can't tell for sure without getting some info from your phone), you should get back 4G.