Shall we have a centralized place for discussion (or better, solutions) related to the bootloop issue happened on HTC One GPe? Apparently I'm not the only one in this situation, and having a single thread will help others to find the solution more easily.
The problems are basically having a soft bricked GPe and only bootloader is accessible. The GPe device is real, S-On, locked or relocked, with stock firmware of OS-3.58.1700.5 and HBOOT 1.54, but without a working rom.
1. flashing the GPe RUU by graffixnyc from this thread won't work because of the signature verification failure, which makes sense since it's not signed by HTC (the firmware.zip flashes through because it's signed by HTC).
2. fastboot oem unlock does not work and shows the following error:
Code:
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.543s]
finished. total time: 0.543s
3. fastboot flash unlocktoken Unlock_code.bin fails silently, i.e. the confirmation screen does not show up on device.
4. trying s-off the device is not feasible without a working rom and unlocked bootloader.
5. fastboot boot <custom_recovery>.img fails for both CWM and TWRP:
Code:
downloading 'boot.img'...
OKAY [ 1.123s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.123s
6. fastboot erase cache and factory reset does not help.
Any other options so we could have a try? @nkk71 @SaHiLzZ
Thank you for creating this thread. The same issue is happening for converted devices with relocked bootloader as well.
I'm out of options as neither fastboot oem unlock nor fastboot flash token unlock.bin are working, and without these not much to do.
SaHiLzZ said:
Thank you for creating this thread. The same issue is happening for converted devices with relocked bootloader as well.
I'm out of options as neither fastboot oem unlock nor fastboot flash token unlock.bin are working, and without these not much to do.
Click to expand...
Click to collapse
It seems like some mechanism has been changed in the latest firmware that prevents the original unlocking method.
This seems to be happening more and more. I'm in the same boat. Tried to update a GPe HTC One and got stuck.
I have contacted HTC support as stated in this thread:
http://forum.xda-developers.com/showthread.php?t=2492469&page=5
They we able to help get his up and running. Hopefully they can help me out to with out the need to pay extra charges.
I will update on the progress, but seeing as we are entering the weekend, it will probably only be next week.
I miss my phone
Thanks for the thread and the clear summary. I have exactly the same issue with my stock Gpe and am anxiously waiting for a solution.
Sent from my Nexus 7 using XDA Premium 4 mobile app
joe7wu said:
It seems like some mechanism has been changed in the latest firmware that prevents the original unlocking method.
Click to expand...
Click to collapse
Create a new unlock_code.bin file using htcdev.com. This worked for me. I tried to use a unlock_code.bin file which i used when using Sense. This older bin-file didn't work so i tried to create a new one. This worked for me and my bootloader is unlocked now.
mderksen said:
Create a new unlock_code.bin file using htcdev.com. This worked for me. I tried to use a unlock_code.bin file which i used when using Sense. This older bin-file didn't work so i tried to create a new one. This worked for me and my bootloader is unlocked now.
Click to expand...
Click to collapse
I think he is talking about the method on the device, not from HTC Dev.
On the device, using "fastboot oem unlock" or the HTC Dev method dosent work.
As stated above the first returns an error and the .bin method shows a success message, but nothing actually happens.
This is my situation anyways.
Any one with locked, not relocked bootloader having the same issue. Wonder how Google will fix this..
+1 I'm having the same problem
Edit: They should make this a sticky thread for as long as the problem exist
I am also having the same issue on my google play edition. S-On. I reflashed a stock recovery image so I could update to stock ROM. Now, I am stuck in a bootloop. I cannot reload any kind of custom recovery (I say that I can't. When I do, the phone will not boot into recovery. It just jumps to the Google screen, attempts to load the OS and then restarts). I AM able to unlock and relock using fastboot oem unlock and lock. I've attempted to reload the firmware and it seems to work (via cmd loading), but the loop process begins again. I attempted to flash a 4.3 firmware I found, but received the blue screen of nothingness when I did.
I'm lost. Possibly only solution is sending back in for repair. I just got the phone and this is annoying as heck..
alcaloide_ said:
+1 I'm having the same problem
Edit: They should make this a sticky thread for as long as the problem exist
Click to expand...
Click to collapse
Yeah, a sticky thread will help a lot. Anyway, I'm still waiting for those people who got in touch with HTC and see how it goes. A bit worried about the fact that I'm in Canada and a friend in US bought this phone for me. Not sure how the custom support will be like in my case.
So, a thought just occurred to me - i haven't updated any of my tools for fastboot since i originally unlocked the system a few months ago.
I am not currently at home, so i cannot check on this, but perhaps this will help others....
The current sdk tools version is 22.3 : http://developer.android.com/sdk/index.html
Could perhaps updating these tools help us re-unlock our phones?
If someone checks and tries this, and then the fastboot oem unlock command, let me know if it is simply a windows software thing.
OK so I emailed HTC, they told me that because the phone was issued from Google, it was Google who was in charge of the warrenty. They gave me the Google customer care number "Google’s US hardware support number: 1.855.836.3987 they are open 24/7." just in case anyone needs it.
I just got off the phone and after talking with them I got the impression that they are aware of the problem but that there is currently nothing that they can do to fix it.
It seemed as though he was hinting at a fix in the future, possibly a flashable zip, but I dont know.
Anyways he had me go into recovery mode, and do a factory reset. I didnt even know I was able to do this. Unfortunately it didn't help.
At the end we had to set up an RMA. They are sending out a phone and then I will need to return mine.
Being currently in Israel they were unable to send it here, so they are going to send it to the US, and they I will send mine back from here.
Kinda sux, I was hoping for a quick fix.
Hope this helps somebody...
AmirH said:
OK so I emailed HTC, they told me that because the phone was issued from Google, it was Google who was in charge of the warrenty. They gave me the Google customer care number "Google’s US hardware support number: 1.855.836.3987 they are open 24/7." just in case anyone needs it.
I just got off the phone and after talking with them I got the impression that they are aware of the problem but that there is currently nothing that they can do to fix it.
It seemed as though he was hinting at a fix in the future, possibly a flashable zip, but I dont know.
Anyways he had me go into recovery mode, and do a factory reset. I didnt even know I was able to do this. Unfortunately it didn't help.
At the end we had to set up an RMA. They are sending out a phone and then I will need to return mine.
Being currently in Israel they were unable to send it here, so they are going to send it to the US, and they I will send mine back from here.
Kinda sux, I was hoping for a quick fix.
Hope this helps somebody...
Click to expand...
Click to collapse
Interesting. I chatted with an HTC rep this morning and I am sending the phone to an HTC repair facility in Houston. I wish Google would just do an exchange. DId they give you a hard time? Should I just call them and ask for an exchange?
They didn't give me a hard time at all. They were actually pretty cool about it.
They tried to help me out, they saw they couldn't, so they said they would send me a new one. I even went as far as telling them that I was playing around with it trying to unlock and flash 4.4(not too specific of course), and that they should just give me a flashable zip to use because I could get it into RUU mode.
I'm not sure if it makes a difference but I bought the phone in August. So i guess the only real question is, is if you still have warranty.
AmirH said:
They didn't give me a hard time at all. They were actually pretty cool about it.
They tried to help me out, they saw they couldn't, so they said they would send me a new one. I even went as far as telling them that I was playing around with it trying to unlock and flash 4.4(not too specific of course), and that they should just give me a flashable zip to use because I could get it into RUU mode.
I'm not sure if it makes a difference but I bought the phone in August. So i guess the only real question is, is if you still have warranty.
Click to expand...
Click to collapse
Thanks! I assume it is a one year warranty? My issue is that I bought it used. I wonder if they will give me a hard time about that.
---------- Post added at 03:48 PM ---------- Previous post was at 03:34 PM ----------
AmirH said:
They didn't give me a hard time at all. They were actually pretty cool about it.
They tried to help me out, they saw they couldn't, so they said they would send me a new one. I even went as far as telling them that I was playing around with it trying to unlock and flash 4.4(not too specific of course), and that they should just give me a flashable zip to use because I could get it into RUU mode.
I'm not sure if it makes a difference but I bought the phone in August. So i guess the only real question is, is if you still have warranty.
Click to expand...
Click to collapse
Well, i just got off the phone with them. I'm glad you had more success than I! The lady said she could not identify a troubleshot and, since I did not buy from them under my account, they couldn't help me.
AmirH said:
OK so I emailed HTC, they told me that because the phone was issued from Google, it was Google who was in charge of the warrenty. They gave me the Google customer care number "Google’s US hardware support number: 1.855.836.3987 they are open 24/7." just in case anyone needs it.
I just got off the phone and after talking with them I got the impression that they are aware of the problem but that there is currently nothing that they can do to fix it.
It seemed as though he was hinting at a fix in the future, possibly a flashable zip, but I dont know.
Anyways he had me go into recovery mode, and do a factory reset. I didnt even know I was able to do this. Unfortunately it didn't help.
At the end we had to set up an RMA. They are sending out a phone and then I will need to return mine.
Being currently in Israel they were unable to send it here, so they are going to send it to the US, and they I will send mine back from here.
Kinda sux, I was hoping for a quick fix.
Click to expand...
Click to collapse
Huh. Interesting. Maybe i just need to call Google. I did try factory reset, but that didn't work. Probably best to do what you did and just ask for a new one to be sent, if they cannot resolve. I did buy it with my google account, so i might be in luck (I probably about when you did, around August).
elisaw99 said:
Huh. Interesting. Maybe i just need to call Google. I did try factory reset, but that didn't work. Probably best to do what you did and just ask for a new one to be sent, if they cannot resolve. I did buy it with my google account, so i might be in luck (I probably about when you did, around August).
Click to expand...
Click to collapse
I would give it a shot
elisaw99 said:
Huh. Interesting. Maybe i just need to call Google. I did try factory reset, but that didn't work. Probably best to do what you did and just ask for a new one to be sent, if they cannot resolve. I did buy it with my google account, so i might be in luck (I probably about when you did, around August).
Click to expand...
Click to collapse
Let us know how it goes! II will be sending mine to HTC tomorrow
I just got off of the phone with Google. Rep indicated that many have been going through this problem. They are sending out a new phone right away and I will send mine back upon receiving the new one. Bought the phone in July from Google Play Store. Great customer service!
Related
So I have a fully stock HTC One and have spent all night trying to unlock the bootloader. Nothing seems to work I have never rooted this phone, everything I have read makes it seem as if it's impossible. I've tried the adb/fastboot, htcdev, and changing CID methods. Plus I have read of various other ways that already require a root. Which I cannot do seeing how I am still locked and S-ON.
To be honest I'm at the edge and I think I'm just going to give up. I'm on 4.2.2 - hboot 1.54. I was a previous owner of the Thunderbolt which was not a bad phone, I rooted that and everything no questions asked. Although I do remember HTC taking the longest for OTA updates, not a huge fan of HTC.
If anyone has any suggestions on how to unlock the bootloader I will be fine from there. I'm positive I have all the right equipment and prerequisites just not sure if I really am at the end of the road.
Anything useful goes a long way right now.
Thanks.....
xxshererxx said:
So I have a fully stock HTC One and have spent all night trying to unlock the bootloader. Nothing seems to work I have never rooted this phone, everything I have read makes it seem as if it's impossible. I've tried the adb/fastboot, htcdev, and changing CID methods. Plus I have read of various other ways that already require a root. Which I cannot do seeing how I am still locked and S-ON.
To be honest I'm at the edge and I think I'm just going to give up. I'm on 4.2.2 - hboot 1.54. I was a previous owner of the Thunderbolt which was not a bad phone, I rooted that and everything no questions asked. Although I do remember HTC taking the longest for OTA updates, not a huge fan of HTC.
If anyone has any suggestions on how to unlock the bootloader I will be fine from there. I'm positive I have all the right equipment and prerequisites just not sure if I really am at the end of the road.
Anything useful goes a long way right now.
Thanks.....
Click to expand...
Click to collapse
what exactly is happening when you try and unlock the bootloader?
xxshererxx said:
So I have a fully stock HTC One and have spent all night trying to unlock the bootloader. Nothing seems to work I have never rooted this phone, everything I have read makes it seem as if it's impossible. I've tried the adb/fastboot, htcdev, and changing CID methods. Plus I have read of various other ways that already require a root. Which I cannot do seeing how I am still locked and S-ON.
To be honest I'm at the edge and I think I'm just going to give up. I'm on 4.2.2 - hboot 1.54. I was a previous owner of the Thunderbolt which was not a bad phone, I rooted that and everything no questions asked. Although I do remember HTC taking the longest for OTA updates, not a huge fan of HTC.
If anyone has any suggestions on how to unlock the bootloader I will be fine from there. I'm positive I have all the right equipment and prerequisites just not sure if I really am at the end of the road.
Anything useful goes a long way right now.
Thanks.....
Click to expand...
Click to collapse
Is urs the AT&T One? Then the bootloader unlock process is different. If urs is the standard international SIM unlocked, then ideally you should see a splash after you run the bootloader unlock command, which prompts you to unlock the bootloader. Please state what exactly ur issue is when u try to bootloader unlock
I'm with Verizon but it just gives me a 1 line error message doesn't run through anything else or load up anything. I type in "bootloader oem unlock" or whatever after clearly identifying my device is connected with "adb device" and nothing happens. It takes about 0.14 sec and says something along the lines of "[ERRORR] ......" after running again it takes 0.00 sec and says same thing, I can screenshot if you think it would be more helpful.
Please help, I appreciate both responses. Just really want this to work.
xxshererxx said:
I'm with Verizon but it just gives me a 1 line error message doesn't run through anything else or load up anything. I type in "bootloader oem unlock" or whatever after clearly identifying my device is connected with "adb device" and nothing happens. It takes about 0.14 sec and says something along the lines of "[ERRORR] ......" after running again it takes 0.00 sec and says same thing, I can screenshot if you think it would be more helpful.
Please help, I appreciate both responses. Just really want this to work.
Click to expand...
Click to collapse
Hahahaha Verizon is REALLY REALLY BAD when it comes to dev. support. Ideally, you shouldn't be posting this in this forum. Post it on the Verizon forum. But, I can help you.
http://rumrunner.us/downloads-2/
Download the package. Extract the zip and run the 'soju.exe' program. Please read ALL the pre-requisites mentioned in the instructions tab.
P.S. From next time if you're asking for help, please state that you're on Verizon
raghav kapur said:
Hahahaha Verizon is REALLY REALLY BAD when it comes to dev. support. Ideally, you shouldn't be posting this in this forum. Post it on the Verizon forum. But, I can help you.
Download the package. Extract the zip and run the 'soju.exe' program. Please read ALL the pre-requisites mentioned in the instructions tab.
P.S. From next time if you're asking for help, please state that you're on Verizon
Click to expand...
Click to collapse
Worked like a charm, but now I am having trouble with the recovery portion of all this.
I have downloaded and installed the TWRP Manager app and then went to install the recovery and it said my device is not supported, this same problem happened with CWMR.
xxshererxx said:
Worked like a charm, but now I am having trouble with the recovery portion of all this.
I have downloaded and installed the TWRP Manager app and then went to install the recovery and it said my device is not supported, this same problem happened with CWMR.
Click to expand...
Click to collapse
I think you'll find more help here: http://forum.xda-developers.com/verizon-htc-one
I recently purchased a nexus 6 off ebay, likely a mistake, and now that I try to run the setup i can't because i'm not the original account on the phone. Is there anything I can do to get past this step, remove the old user account and add myself to the phone? I know the security measure was put in for a reason, but it definitely makes it hard when someone like me gets the phone and is now stuck with a good looking paperweight. I have tried contacting the seller and getting them to provide me with their info for the purposes of setting it up but they are reluctant to offer that up. Unsurprisingly.
Any help would be appreciated.
Thank you,
Fk
fkoulbot said:
I recently purchased a nexus 6 off ebay, likely a mistake, and now that I try to run the setup i can't because i'm not the original account on the phone. Is there anything I can do to get past this step, remove the old user account and add myself to the phone? I know the security measure was put in for a reason, but it definitely makes it hard when someone like me gets the phone and is now stuck with a good looking paperweight. I have tried contacting the seller and getting them to provide me with their info for the purposes of setting it up but they are reluctant to offer that up. Unsurprisingly.
Any help would be appreciated.
Thank you,
Fk
Click to expand...
Click to collapse
I'm sorry but the only way is with that password. This is fault of the seller, they did a factory reset without removing their Google account. If the seller won't help you, contact eBay resolution center.
@fkoulbot,
Unfortunately, plenty of threads here with the same situation.
What @Evolution_Freak said, or open a PayPal claim. Device "Significantly Not As Described". You'll get your money back.
Or, just post it back to him at his expense, and get him to do it properly.
"Hi,
I understand that you feel uncomfortable giving me your Google password. Since the phone is unusable without it, I will have to consider opening a paypal dispute.
To avoid this however, if you offered to cover the cost of 2 way postage of the device (+insurance), I could send the device to you to log into and remove your account properly before resetting and returning to me."
fkoulbot said:
I recently purchased a nexus 6 off ebay, likely a mistake, and now that I try to run the setup i can't because i'm not the original account on the phone. Is there anything I can do to get past this step, remove the old user account and add myself to the phone? I know the security measure was put in for a reason, but it definitely makes it hard when someone like me gets the phone and is now stuck with a good looking paperweight. I have tried contacting the seller and getting them to provide me with their info for the purposes of setting it up but they are reluctant to offer that up. Unsurprisingly.
Any help would be appreciated.
Thank you,
Fk
Click to expand...
Click to collapse
Hey, buddy. I had the same thing happen to me on Swappa. Fortunately the guy was willing to give me his password... BUT in the 2 hours it took him to respond to my dilemma, I had already found a way around it. (Take note that my bootloader was already unlocked when I received the device.) Here's what I did.....
I tried flashing a couple different ROMs to no avail.
Then I realized it was because I was flashing 5.1 ROMs.
So, I found a 5.0.1 ROM that doesn't have the reactivation built in, flashed it, got it set up, then flashed a new 5.1 ROM. It worked for me but YMMV. I do believe having an unlocked bootloader in the first place helped. Hope that helps.
hyst3rical said:
Hey, buddy. I had the same thing happen to me on Swappa. Fortunately the guy was willing to give me his password... BUT in the 2 hours it took him to respond to my dilemma, I had already found a way around it. (Take note that my bootloader was already unlocked when I received the device.) Here's what I did.....
I tried flashing a couple different ROMs to no avail.
Then I realized it was because I was flashing 5.1 ROMs.
So, I found a 5.0.1 ROM that doesn't have the reactivation built in, flashed it, got it set up, then flashed a new 5.1 ROM. It worked for me but YMMV. I do believe having an unlocked bootloader in the first place helped. Hope that helps.
Click to expand...
Click to collapse
Thanks so much for that info. I had actually received and tried that but because it wasn't unlocked i was stuck. I did get the login info but now worried that they somehow have access to the phone. I noticed the label of a "group" of apps on my home screen was randomly changed. I did DL an antivirus app and it found something but I'm still worried about the security of the phone. Do you happen to have any suggestion on the best thing i can do to absolutely clear any of the old account information etc?
fkoulbot said:
Thanks so much for that info. I had actually received and tried that but because it wasn't unlocked i was stuck. I did get the login info but now worried that they somehow have access to the phone. I noticed the label of a "group" of apps on my home screen was randomly changed. I did DL an antivirus app and it found something but I'm still worried about the security of the phone. Do you happen to have any suggestion on the best thing i can do to absolutely clear any of the old account information etc?
Click to expand...
Click to collapse
First thing I would do is go into Settings -> Accounts and remove the Google account that it was originally linked on. Then add your own. Do a factory reset, and you should be fine. If you want to go the extra mile, set up the reactivation lock under your account. I do believe that should clear any permissions he may still have as they would be linked to his Google account.
fkoulbot said:
Thanks so much for that info. I had actually received and tried that but because it wasn't unlocked i was stuck. I did get the login info but now worried that they somehow have access to the phone. I noticed the label of a "group" of apps on my home screen was randomly changed. I did DL an antivirus app and it found something but I'm still worried about the security of the phone. Do you happen to have any suggestion on the best thing i can do to absolutely clear any of the old account information etc?
Click to expand...
Click to collapse
Boot to bootloader.
Fastboot format userdata
(Note that this will wipe everything, including contents of SDcard.
I would lock then unlock bootloader which would wipe the phone and then go to google and download latest builds and flash the phone to factory stock. Boot in, if there isn't anything funky, then I would made a backup of the stock and flash custom ROMs from that point. I like to check first if it works bone stock wiped before tinkering. That way if anything is still wrong with it I know who's at fault.
farangutan said:
I would lock then unlock bootloader which would wipe the phone and then go to google and download latest builds and flash the phone to factory stock. Boot in, if there isn't anything funky, then I would made a backup of the stock and flash custom ROMs from that point. I like to check first if it works bone stock wiped before tinkering. That way if anything is still wrong with it I know who's at fault.
Click to expand...
Click to collapse
Why would you lock the bootloader? If you want everything wiped do > fastboot format userdata
cam30era said:
Why would you lock the bootloader? If you want everything wiped do > fastboot format userdata
Click to expand...
Click to collapse
Well, more likely if it's locked I would just unlock, but yes the act of flashing it to factory images will wipe in one go. Relocking and unlocking is redundant.
Guys does anyone confirm that is any way you can remove the Google Account Lock on Nexus 6 that the previous seller didn't remove the Goggle Account?
Thanks in advance!
Im having the same dang issue!! Hopefully I can get it flashed since sell won't give me password.
I'm running a P7 with the firmware it shipped with and I'd really like to get it up to date, but every package I've tried so far has failed during package verification. There seems to be very little info on how to update your phone from such an old build. Can anyone please help because I'm at my wit's end here. I have a limited date cap so can't just keep downloading updates in the hopes that one of them will work.
I would be greatly indebted to anyone who could help me. This issue is making me want to cry.
Do you have a phone with a provider/network lock? Which roms did you try so far? You may give B133 a shot, if that doesn't work you'd have to go the way over a custom rom and then getting back to the stock one. I can describe the process more detailed in case it's necessary.
Thanks for the response!
I think the issue is that it is a network locked ROM. I got the phone from a provider called Vodacom and get their splash screen and everything. I went to speak to them and they told me I'm not supposed to be able to update my firmware because that requires rooting the phone, which voids my warranty. Sales people being sales people, I'm not sure how truthful this is. I can't imagine a provider refusing to let you update your phone.
So far I've tried B133, B609, B617 and B853, none of which works, sadly. Someone suggested I unlock the bootloader and I got the unlock code through the Huawei site, but when I try to boot using the three-button method it tells me that no update.app file was found, so I'm not sure how to get to where I enter the unlock code.
Hm, you might search around a bit and find an easier way, but if not, unlock the bootloader, flash twrp and any emui 2.3 based custom rom. Then flash the stock recovery and make a forced update (3 buttons) with B133.
To access the bootloader you have to press volume- and power until a white screen with some text appears.
Anyway, to update would definitely be worth it.
Yeah, I did precisely that last night and ended up soft-bricking my phone. It wouldn't even work when I flashed the original firmware. It's currently in at a repair shop and I hope they can fix it. Lesson learned though.
Thanks for the help anyway.
It's not that easy to hardbrick the P7, it's very likely that he will be able to fix it! With some time for trying, you probably would have been able to do it by yourself, too.
Your very welcome
Yeah, the thing is I was up all night trying to fix it. Flashing it back the original software should theoretically have done it, so I have no idea why it didn't.
Ive had this problem for ages and tried everything i can think of. hopefully by now someone has experienced the same problem and solved it.
*My phone is stuck on honor boot logo
*i can access e-recovery
*i can access stock recovery
*i can access fastboot and device is recognised on my laptop
* i can wipe cache and factory reset successully and have done many times
*i can and have used the dload (3 button method) to flash stock rom successfully
Now the problem is that although i have flashed the earliest stock rom NEM-L51C432B102 it fails saying incorrect package!!!i think this is because my phone came with B103 or B104 and you can only flash from what your phone originally had and up.
I have flashed NEM-L51C432b120 and also NEM-L51C432b130 and although it says successful it reboots and remains stuck on honor boot logo!
I have entered fastboot and i can issue commands but they all fail saying REMOTE COMMAND NOT ALLOWED.
I can't use ADB because it doesn't recognise my device. Obviously ADB and FASTBOOT wont work because i can't access developper options and select enable USB debugging or OEM Unlock because the phone is stuck on honor boot logo.
Also my bootloader must be locked. I have the unlock code but i can't issue the command FASTBOOT OEM UNLOCK XXXXXXXXXXXXXXX because as mentioned before it says FAILED REMOTE COMMAND NOT ALLOWED.
I have even tried flashing rollback packages(there isnt one for NEM-L51)for other models, followed by flashing stock rom for my model device.
When i bought the phone it came with either the B103 or B104 package but after months of searching i can't find on the internet.
Is my phone a lost cause??? is it hard bricked? So i am praying that there is a guru out there who can solve this very strange problem.
Many thanks in advance.
iantechie1979 said:
Ive had this problem for ages and tried everything i can think of. hopefully by now someone has experienced the same problem and solved it.
*My phone is stuck on honor boot logo
*i can access e-recovery
*i can access stock recovery
*i can access fastboot and device is recognised on my laptop
* i can wipe cache and factory reset successully and have done many times
*i can and have used the dload (3 button method) to flash stock rom successfully
Now the problem is that although i have flashed the earliest stock rom NEM-L51C432B102 it fails saying incorrect package!!!i think this is because my phone came with B103 or B104 and you can only flash from what your phone originally had and up.
I have flashed NEM-L51C432b120 and also NEM-L51C432b130 and although it says successful it reboots and remains stuck on honor boot logo!
I have entered fastboot and i can issue commands but they all fail saying REMOTE COMMAND NOT ALLOWED.
I can't use ADB because it doesn't recognise my device. Obviously ADB and FASTBOOT wont work because i can't access developper options and select enable USB debugging or OEM Unlock because the phone is stuck on honor boot logo.
Also my bootloader must be locked. I have the unlock code but i can't issue the command FASTBOOT OEM UNLOCK XXXXXXXXXXXXXXX because as mentioned before it says FAILED REMOTE COMMAND NOT ALLOWED.
I have even tried flashing rollback packages(there isnt one for NEM-L51)for other models, followed by flashing stock rom for my model device.
When i bought the phone it came with either the B103 or B104 package but after months of searching i can't find on the internet.
Is my phone a lost cause??? is it hard bricked? So i am praying that there is a guru out there who can solve this very strange problem.
Many thanks in advance.
Click to expand...
Click to collapse
Oh well. Seriously this is the same issue my frn asked me to help. This is soo serious that we can only unbrick through update.app or else service center. Since u said dload method works but stucks device on bootlogo. U need to visit service center if under Warranty
iantechie1979 said:
When i bought the phone it came with either the B103 or B104 package but after months of searching i can't find on the internet.
Is my phone a lost cause??? is it hard bricked? So i am praying that there is a guru out there who can solve this very strange problem.
Many thanks in advance.
Click to expand...
Click to collapse
Flash these files and it should, most probably, be fine.
use dload method as given here- https://forum.xda-developers.com/showpost.php?p=73954487&postcount=240
as there are many different opinions on this method of using only update.app file but thats not true and it should be all the files.
Main file - http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1165/g104/v71812/f1/full/update.zip
Data file- http://update.hicloud.com:8180/TDS/...1812/f1/full/hw/eu/update_data_full_hw_eu.zip
Flash both the files in order. 1st file will restore your system but then you need to have 2nd file so that apps are installed and all working fine.
After 1st file, it may reboot on its own and stuck on honor logo, reboot to recovery and then do factory reset, it will be fine.
Then let it boot to set up. Dont set your phone. Shutdown and flash the 2nd file.
boot and set up.
Good luck. Please provide feedback once done. In case of further issue, let me know and will dig more into this.
Oh this is hard.
chrisleLP said:
Oh this is hard.
Click to expand...
Click to collapse
What is hard?
shashank1320 said:
What is hard?
Click to expand...
Click to collapse
This problem.
chrisleLP said:
This problem.
Click to expand...
Click to collapse
you cant follow simple instructions? you shouldnt be on this forum if youre not ready to lose data or brick your device.
Thanks for your input so far people. Much appreciated. @shashank1320 I am downloading the files you suggested and will flash them exactly according to your instructions. I will get back to you in a couple of days with the result. Fingers crossed.
gopinaidu77 said:
Oh well. Seriously this is the same issue my frn asked me to help. This is soo serious that we can only unbrick through update.app or else service center. Since u said dload method works but stucks device on bootlogo. U need to visit service center if under Warranty
Click to expand...
Click to collapse
Unfortunately my warranty has expired. The annoying thing is that if i had sent my device off six months ago when this first happened it would still be under warranty but in the UK there is only 1 service center, yes 1, and its hundreds of miles away! So i figured i could solve it myself. You live and learn.
Hey there everyone. I still havent managed to solve the issue with my device and its not through lack of trying. I have re downloaded all of the stock firmwares that you can possibly find on the internet. I also found one ive necer seen before. Its a full service repair b355. Fingers crossed, a miracle might happen and it will just boot up like when i first bought it. to begin with tho, i'm going to start with b102 and work through them b120, b130 ,b130rollback ,b350(beta), b350, b355 and then the b355 full service repair! I also got a couple of rollback packages(around 80mb) if all else fails.
I know, i'm nuts!! Finally before i admit defeat i'm going to part with £15 to buy credits for the dc-unlocker and dcPhoenx programs. From what ive read it has a good chance of solving it. I've taken soooo long before considering this option because i think its wrong that someone(s) is making loads of money from this. Why havent huawei/honor included a similar program in hi-suite. Anyway ive gone off on a tangent.
One last question though. Strangely enough i only just thought of it recently....
Is it a necessity to have your sim card in the tray as well as the sd-card????? All this time i havent had a sim in the phone as its in a crappy old one so i can still communicate with the world!!!!
Thank you to everyone for taking your time to read this. I hope a solution is possible.
iantechie1979 said:
Hey there everyone. I still havent managed to solve the issue with my device and its not through lack of trying. I have re downloaded all of the stock firmwares that you can possibly find on the internet. I also found one ive necer seen before. Its a full service repair b355. Fingers crossed, a miracle might happen and it will just boot up like when i first bought it. to begin with tho, i'm going to start with b102 and work through them b120, b130 ,b130rollback ,b350(beta), b350, b355 and then the b355 full service repair! I also got a couple of rollback packages(around 80mb) if all else fails.
I know, i'm nuts!! Finally before i admit defeat i'm going to part with £15 to buy credits for the dc-unlocker and dcPhoenx programs. From what ive read it has a good chance of solving it. I've taken soooo long before considering this option because i think its wrong that someone(s) is making loads of money from this. Why havent huawei/honor included a similar program in hi-suite. Anyway ive gone off on a tangent.
One last question though. Strangely enough i only just thought of it recently....
Is it a necessity to have your sim card in the tray as well as the sd-card????? All this time i havent had a sim in the phone as its in a crappy old one so i can still communicate with the world!!!!
Thank you to everyone for taking your time to read this. I hope a solution is possible.
Click to expand...
Click to collapse
No need of sim card in tray while using dload. Just sd card is fine. Let me go through it again and try to help before you go for 15 dollars for dc phoenix
shashank1320 said:
No need of sim card in tray while using dload. Just sd card is fine. Let me go through it again and try to help before you go for 15 dollars for dc phoenix
Click to expand...
Click to collapse
Yeah i didn't think it made any difference but its good to make sure.
i'll be waiting patiently for any golden nuggets of help you can give me.
thanks shashank1320,:fingers-crossed:
iantechie1979 said:
Yeah i didn't think it made any difference but its good to make sure.
i'll be waiting patiently for any golden nuggets of help you can give me.
thanks shashank1320,:fingers-crossed:
Click to expand...
Click to collapse
Did you flash those files i given? If not can try. Else i will have to look for other alternative
yeah i downloaded those files you had mentioned in your post and followed the instructions to the letter.
I've got a suggestion if you have tried all these above.
Can you try the following on ADB and then try to unlock OEM again.
fastboot oem relock YourUnlockCode
I've done the same and it helped, even when bootloader displayed UNLOCKED. Please try it. :good::good:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
@shashank1320 Hi, i have similar problem with my NEM-L21 device... I tried to flash the Elite ROM v5.1 but i didnt succeed so i decided to restore my old rom from backup with TWRP. When i restored it it just didnt load. It was stuck on honor logo for a long time. I tried the dload method many times but nothing worked so far. I even tried unbrick it with HUAWEI Multi-tool but it also didnt worked.
Now i cant acces anything, just fastboot. I cant even turn off the device. Please can you help me somehow?
NameNotFound74 said:
@shashank1320 Hi, i have similar problem with my NEM-L21 device... I tried to flash the Elite ROM v5.1 but i didnt succeed so i decided to restore my old rom from backup with TWRP. When i restored it it just didnt load. It was stuck on honor logo for a long time. I tried the dload method many times but nothing worked so far. I even tried unbrick it with HUAWEI Multi-tool but it also didnt worked.
Now i cant acces anything, just fastboot. I cant even turn off the device. Please can you help me somehow?
Click to expand...
Click to collapse
Try unlocking the bootloader again even if it is unlocked. It will factory reset the device and it should boot fine. Have stuck on this many a time and this was the method i followed.
Foreword: My time with Vivo has come to an end. After flashing a wrong devicecfg and accidentally rebooting my device it is now in a hard bricked state.
Vivo has locked down EDL, there is absolutely no way to flash or backup anything in EDL mode without the official Tools (namely Vivo AFTool 5.9.80).
Vivo India refers me to Vivo Germany - Vivo Germany has outsourced its customer support to bulgaria.
The people on the other side of the line know absolutely nothing about the technical aspect and refuse to put me through to anyone with any kind of knowhow.
Due to their anti consumer and anti repair attitudes I will not buy another Vivo phone.
With this out of the way: You might end up like me with a hard brick. Or without signal.
Even if this will not save you from a hard brick I can not stress this enough: Make a BACKUP! And backup your data. This will wipe your phone.
This process is IRREVERSIBLE unless you have a split ROM of the chinese Firmware or your own Backup.
THIS or BL UNLOCK will break your portrait mode. No more bokeh, neither in Origin OS nor FunTouch.
Do NOT flash fsg, modemst1 and modemst2. They are commented out in the COMMANDS file.
You do this at your own risk. As said before this might brick your device.
Unlock your Bootloader
Backup your Partitions
Download my Flash Folder and Extract it: Android File Host
Open 01COMMANDS.txt and read the instructions
Open a command shell in the same folder that you can find 01COMMANDS.txt in
Run the given commands in blocks or one after the other
If you do not have signal after flashing you might have to erase modemst1 and modemst2 partitions, so that they get replaced by the backup in fsg.
A magisk flashed boot.img and adb-modded recovery is included so you can flash it after booting up FunTouch once and backup all your partitions again.
Thanks again to @Pervokur for helping me along the way. There is definitely an easier method that involves less risky flash operations.
My phone died on the cross while I was trying to figure it out, so maybe someone else will pick up the torch.
I will not be able to offer any kind of support.
RIP @Killuminati91's Vivo, who died for the cause.
Sorry to hear that, man, you were so close to what looked like an easy switch between ROMs.
I know you said you were no developer but you are still a leap ahead of most of us here. Long do we miss the good old days where ROMs, kernels and pure innovation shortly followed our much-wanted phone when flashing a few ROMs a week was normal.
Thanks for all your help, perhaps one day there will be a way to recover your phone.
Many thanks, may I relock the bootloader when i finished change to Global rom?
amos0609 said:
Many thanks, may I relock the bootloader when i finished change to Global rom?
Click to expand...
Click to collapse
Same question
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
how did you relock the bootloader, does the portrait mode work again?
does any one change the origin os /ocean into funtouch？
version？ how to relock after it can switch to funtouch？
by the way, I saw the post on the taiwan vivo phone of fb
the second hand goods, it wrote he change the origin os into funtouch
and he sell this service , it charge 2000 nt dollars in taiwan.
maybe someone can save your phone.
Killuminati91
I think the only problem that keeps the phone from being recognized as official FunTouch is dm-verity.
In theory both phone versions have the same exact hardware.
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
stevenkh168 said:
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
Click to expand...
Click to collapse
Message?
silence360 said:
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
Click to expand...
Click to collapse
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Killuminati91 said:
Message?
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Click to expand...
Click to collapse
did you try using the OriginOS's camera app on FuntouchOS ? I find it when u use the front facing camera, the portrait mode still work. In the other hand, the back camera is not working in portrait mode. I follow your guide and using the FuntouchOS about 2 days. Everything works fine, except the portrait mode and the AOD. Cant use it anymore.
Oh I see, now that is weird that the portrait mode is not working. So even if you switch not all functionality has returned. Thanks for the explanation. Hopefully someone can continue your work, and find a solution for a seamless transition.
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
hope to see some good news from you sir.
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
Update us...
have you been able to solve it?
amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
NHQ Thang said:
how did you relock the bootloader, does the portrait mode work again?
Click to expand...
Click to collapse
same question
adkana4310 said:
Update us...
have you been able to solve it?
Click to expand...
Click to collapse
If u asking me so no im still on the same cant flash
redwatch99 said:
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Click to expand...
Click to collapse
Someone who can help me solve it ?