Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Hi, back again
As i can see, try not to mess with the names :revocery...
When you want to flash the boot.img don't change that name.
Just flash it like : fastboot flash boot boot.img
Use my last boot.img which i sent you. That's a good one out of my backup.
For the FRP (perhaps edit your thread tiltle ) i have no answer in a minute. Did the "fastboot oem unlock" gave anything better ?
raystef66 said:
Hi, back again
As i can see, try not to mess with the names :revocery...
When you want to flash the boot.img don't change that name.
Just flash it like : fastboot flash boot boot.img
Use my last boot.img which i sent you. That's a good one out of my backup.
For the FRP (perhaps edit your thread tiltle ) i have no answer in a minute. Did the "fastboot oem unlock" gave anything better ?
Click to expand...
Click to collapse
I have try also boot , try everything, not matter if youhave FRP lock fastboot oem unlock is only to unlock bootloader, which i have, that is not a problem.
See if this method works for you
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
joyrida12 said:
See if this method works for you
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You cannot use this method since i have only FastBoot feature, adb is not possible to use, since phone never boot. This method can be used only for phones what can boot correctly, so unfortunately useless for me. but thx for link
michalss said:
You cannot use this method since i have only FastBoot feature, adb is not possible to use, since phone never boot. This method can be used only for phones what can boot correctly, so unfortunately useless for me. but thx for link
Click to expand...
Click to collapse
i have exactly the same problem. FRP is locked but my phone doenst boot. so how can i unlock the frp with the fastboot mode?
stiggu said:
i have exactly the same problem. FRP is locked but my phone doenst boot. so how can i unlock the frp with the fastboot mode?
Click to expand...
Click to collapse
same problem on my mate s
good to know that adb is not working for others
i thaught it was just me
I've the same problem , any idea ??
michalss said:
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Click to expand...
Click to collapse
activate "Developer options"
playing several times "compilation"
go to options and enable developer
"Enable OEM unlock"
Hey , the problem is the device won't boot , so how can we enable developer option?!!!!
Sent from my iPhone using Tapatalk
There was a time when xda where the place to get the right answer and quick!
nowadays most topics are full of people with same problem and no dev to come to help, pity.
on topic: I have the same problem, ( mine is a Y6 pro) and before bricking it I had debugging and oem unlock enabled but now can't flash boot etc using fastboot ( error , denied ..) and can't use spflashtools either : preloader vcom appears for 1 second and then disappears and phone turns on.
tried many drivers, 3 Os'es (7, 8.1 ,10) still no luck.
porcha18 said:
activate "Developer options"
playing several times "compilation"
go to options and enable developer
"Enable OEM unlock"
Click to expand...
Click to collapse
Danke!!!!!!!!!!!!! Nach ewigem Suchen diese einfache Lösung. Vielen Dank!! Tag gerettet
the same issue
Good day, i have the same issue on my p9 EVA-L19.
FRP lock. And i can't do anything...
My warranty says that they cannot recover data from the phone, but the information is very important. I need to unlock FRP and somehow boot into TWRP or something to recover my data.
Please help someone if you had a same issue and results.
For the Huawei Y6 you can return to Stock.
Try to fastboot boot recovery-twrp.img and put your stock firmware (dload) folder to the rootdir at your sdcard.
Reboot your device to bootloader and hold down vol+ + vol- and use the command: fastboot boot stockrecovery.img (keep the keys pressed until the stock recovery comes up and starts installing your stock rom.
You will see an emui logo and the recovery will install the complete stock rom if you did everything right.
Retry to boot the stock recovery with this way if it is not working at the first try.
EDIT: after i wiped /system and and all the other stuff i was able to flash stock recovery via fastboot.
Runner85sx said:
For the Huawei Y6 you can return to Stock.
Try to fastboot boot recovery-twrp.img and put your stock firmware (dload) folder to the rootdir at your sdcard.
Reboot your device to bootloader and hold down vol+ + vol- and use the command: fastboot boot stockrecovery.img (keep the keys pressed until the stock recovery comes up and starts installing your stock rom.
You will see an emui logo and the recovery will install the complete stock rom if you did everything right.
Retry to boot the stock recovery with this way if it is not working at the first try.
EDIT: after i wiped /system and and all the other stuff i was able to flash stock recovery via fastboot.
Click to expand...
Click to collapse
Is there a way to do this on a mac?
Ive got adb enabled on terminal and I have a recovery.img file in my downloads though Im not sure if its the right one.
I typed in fastboot devices and then fastboot flash recovery recovery.img but it said cannot load recovery.img
anditan said:
Is there a way to do this on a mac?
Ive got adb enabled on terminal and I have a recovery.img file in my downloads though Im not sure if its the right one.
I typed in fastboot devices and then fastboot flash recovery recovery.img but it said cannot load recovery.img
Click to expand...
Click to collapse
your recovery location in adb is wrong probably. try changing it to the correct path. atleast thats what worked for me
man u can'T do anything because FRP is ACTIVATED !!!
No solution till now
Use the Huawei Swype bypass Method
michalss said:
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Click to expand...
Click to collapse
Try to do:
fastboot boot recovery.img
This will boot up the device with the given image. With that you can put a custom rom to your sd-card and flash it.
I will upload a Nandroid (stock system, recovery, boot) from my Y6 SCL-L01 soon.
With that you can restore boot and recovery with twrp. For this way you don't need to have a frp unlock.
Procedure:
fastboot boot recovery-twrp.img
Put your stock firmware (dload folder) to the sdcard.
Put my Nandroid to your sdcard.
Restore my Nandroid, reboot your device with Vol+ and Vol- pressed.
This way only works for SCL-L01 up to SCL-L04.
I need to create an extra recovery.img that includes a dt image that fits for all SCL variants.
Work in progress...
I have just removed frp today, but its not free method, unfortunately
Related
Hi,
First of all sorry for crappy links, but as a new user I cannot post them.
I have got a chinese phone called Haier W858 (imei.info/phonedatabase/15302-haier-w858/). Few days ago I found out that it is similar to Smartfren Andromax I3S and managed to modify stock ROM by fastboot without any problems (current ROM: needrom.com/download/smartfren-andromax-ad682h/). After that when I tried to turn on fastboot mode I got information that bootloader is locked and I need verify.zip file on sdcard to unlock it. Few searches later I found correct verify.zip file and put it on sdcard. Everything should be great, because now when I try to run fastboot mode I get information that verify.zip file is correct and phone turns into some kind of fastboot mode, but I cannot write anything to it.
For example, I get messages like:
Code:
> fastboot flash modem modem\NON-HLOS.bin
sending 'modem' (31985 KB)... OKAY
writing 'modem'... [B]FAILED (remote: can't flash Partition)[/B]
When I check if bootloader is unlocked by fastboot oem device-info I get:
Code:
>fastboot oem device-info
... INFO Device tampered: true
[B]INFO Device unlocked: true[/B]
INFO Charger screen enabled: true
OKAY
so it looks like everything should be alright.
Whatsmore, I can write any ROM by doing it like so:
- turn into that weird fastboot mode,
- boot up into TWRP or CWM by writing: fastboot boot recovery.img (because of this problem I cannot flash it permanently so I boot it up),
- install ROM from recovery.
What my question is - is it possible to flash previous fastboot mode where I could write anything to phone without problems and without checking any verify.zip file?
I do not know if it could help in anything but this is shot made when I did not have correct verify.zip file: postimg.org/image/u7thz6tq7/. Now it says that it is OK and boots up into that weird fastboot mode.
Thanks in advance.
Are you trying to flash a modem from a Samsung phone? Haven't seen NON-HLOS.bin files used in other phones before. That would explain why it wouldn't flash through fastboot...
es0tericcha0s said:
Are you trying to flash a modem from a Samsung phone? Haven't seen NON-HLOS.bin files used in other phones before. That would explain why it wouldn't flash through fastboot...
Click to expand...
Click to collapse
Hard to say if it is modem from Samsung phone, because all of ROMs for this kind of phone got that file. Maybe it is based on Samsung soft... I did not have any problems with flashing this and other files once with fastboot (first flash that I made was with ROM from this site: needrom.com/download/smartfren-andromax-ad682h/) and it was successful, but after that I get messages that I wrote in 1st post.
Any advices?
EDIT: ALSO, use usb 2.0 ports to flash stuff, usb 3.0 is not working 100 percent yet.
EDIT, 14 Mar 2016: Kingroot got me to root and now I have twrp installed, http://www.kingroot.net/ .
I have a Sprint prepaid Moto E 2015 LTE, XT1526. I did the motorola bootloader unlock, that went fine.
The phone works and is activated on RingPlus, when it boots, I get the Red Warning, Bootloader unlocked, when normally booting.
When I try to flash a recovery to the phone (all that I could find here on XDA), I get this response:
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot devices
TA0XXXXXXX fastboot (edited to take out SN)
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (12916 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.015s
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>adb kill-server
I've tried everything, and am providing as much info as I can, in case anyone seeing something that is 'new' or 'different' about my phone.
Double check and be sure you're attempting to flash the TWRP for the Moto E 2015 LTE "Surnia", not "Otus" (which is the Moto E 2015 3G). iirc, I used Squid's TWRP from here: http://forum.xda-developers.com/moto-e-2015/development/twrp-squid-twrp-recovery-moto-e-lte-t3137649 . If 3.0.0 doesn't work, try 2.8.7.
You should also try changing USB ports. I ran into a similar issue where I wasn't able to flash things when I plug into my most often used USB port. I suspect that the contacts got worn from how often I used it, so I tried another USB port and it worked fine.
I have done same procedure as yours and meet same problem yesterday.
I flashed twrp recovery with following command,
fastboot boot recovery.img
instead of
fastboot flash recovery recovery.img
here are the post which I followed.
http://www.xda-developers.com/how-to-root-the-moto-e-2015-and-unlock-the-bootloader-xda-tv/
http://forum.xda-developers.com/moto-e-2015/orig-development/twrp-moto-e-2015-recovery-t3049726
faheyd said:
When I try to flash a recovery to the phone (all that I could find here on XDA), I get this response:
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot devices
TA0XXXXXXX fastboot (edited to take out SN)
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (12916 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.015s
Click to expand...
Click to collapse
Thanks, but not working:
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot boot recovery.img
downloading 'boot.img'...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.009s
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>
You can get rid of the warning by method in post 2 of this link
http://forum.xda-developers.com/moto-e-2015/general/guide-unlock-bootloader-moto-e-2015-t3045748
Q1:How to remove the unlocked bootloader message?
Then, flash the twrp recovery again. Make sure you have right recovery.img. here is the one I used.
http://forum.xda-developers.com/devdb/project/?id=8591#downloads
llaalways said:
You can get rid of the warning by method in post 2 of this link
http://forum.xda-developers.com/moto-e-2015/general/guide-unlock-bootloader-moto-e-2015-t3045748
Q1:How to remove the unlocked bootloader message?
Then, flash the twrp recovery again. Make sure you have right recovery.img. here is the one I used.
http://forum.xda-developers.com/devdb/project/?id=8591#downloads
Click to expand...
Click to collapse
I know that, does not help. I've tried that recovery, one from cyanogenmod also, the recovery img is not the problem. Thanks anyway.
go to phone options and turn on USB debugging and when you go to flash it..
- turn off phone.
- hold volume down and power to get to boot loader screen..
Leave it there and connect to PC.
It should be showing you the bootloader screen.. you know what that is right ?
Then open "Minimal ADB and Fastboot" install folder..
Right click empty folder space while holding shift key down..
Select open cmd window here..
type in either,
fastboot devices
or
mfastboot devices
and make sure it says your device is listed
then paste into cmd window..
mfastboot flash recovery recovery.img
make sure your new recovery file has that name and is copied to that fastboot folder.
that should be it..
xpmule said:
go to phone options and turn on USB debugging and when you go to flash it..
- turn off phone.
- hold volume down and power to get to boot loader screen..
Leave it there and connect to PC.
It should be showing you the bootloader screen.. you know what that is right ?
Then open "Minimal ADB and Fastboot" install folder..
Right click empty folder space while holding shift key down..
Select open cmd window here..
type in either,
fastboot devices
or
mfastboot devices
and make sure it says your device is listed
then paste into cmd window..
mfastboot flash recovery recovery.img
make sure your new recovery file has that name and is copied to that fastboot folder.
that should be it..
Click to expand...
Click to collapse
As stated in my OP, I've done all that, but I'll do it again, please look at my pics and post, you'll see I've done all that already:
S:\Phones\Moto_E-2015-2ndGen-XT1526\mfastboot-v2>mfastboot devices
TA00000000 fastboot (edited to change serial number)
S:\Phones\Moto_E-2015-2ndGen-XT1526\mfastboot-v2>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (12916 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.007s
S:\Phones\Moto_E-2015-2ndGen-XT1526\mfastboot-v2>
Can a DEV please help ? If I need to go back to stock I'll be glad to do it and then unlock the bootloader again, however, I've posted in two diff forums trying to get someone to tell me the correct SPRINT img to bring back to stock, no answers.
XT1526_SURNIA_USC_5.0.2_LXI22.50-29.1_cid9_subsidy-DEFAULT_CFC.xml
XT1526_SURNIA_REPW_5.0.2_LXI22.50-56-1.1_cid6_subsidy-REPUB_CFC.xml
XT1526_SURNIA_BOOST_5.0.2_LXI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml
I think it's the boost, but it doesn't have the SPRINT label on it, like my phone.
You just said,
"Can a DEV please help ? If I need to go back to stock I'll be glad to do it and then unlock the bootloader again"
So why would you say that ?
Did you relock your bootloader ?
Maybe that is why you are having a problem ?
I never have relocked mine eh..
And i have had no problem flashing TWRP from Squid.. all his various updates overwriting the old one.
I have flashed a bunch of stock retail recoveries too and all of those worked fine too.
I am curious did you try and load recovery after to see if it actually changed or not ?
EDIT:
Can i ask you exactly what Custom Recovery you are trying to install ?
And did you verify the MD5 hash ?
I always do *if it's available..
xpmule said:
You just said,
"Can a DEV please help ? If I need to go back to stock I'll be glad to do it and then unlock the bootloader again"
So why would you say that ? On other models of phones it has solved a problem of this nature.
Did you relock your bootloader ? Of course not, if you had read the post, you would see that.
Maybe that is why you are having a problem ? No
I never have relocked mine eh.. Good for you, that doesn't help me.
And i have had no problem flashing TWRP from Squid.. all his various updates overwriting the old one.
I have flashed a bunch of stock retail recoveries too and all of those worked fine too. Good for you, that doesn't help me.
I am curious did you try and load recovery after to see if it actually changed or not ? I did, I get an icon with something that says no cmd,
EDIT:
Can i ask you exactly what Custom Recovery you are trying to install ? Surnia and CM's recovery, no difference.
And did you verify the MD5 hash ? Yes.
I always do *if it's available..
Click to expand...
Click to collapse
I've done all those things and tried to post as much info in my OP. Is there a Dev that can help me?
I've now tried to go back to stock in an effort to unlock this biatch using XT1526_SURNIA_BOOST_5.0.2_LXI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml, and it wont let me do that either. It's not letting me write to the GPT partition. This leads me to believe my phone is NOT unlocked, even though the bootloader shows UNLOCKED BOOTLOADER. Anyone know an answer?
I noticed something a while back when I attempted to flash recovery on a different phone (nexus 6) but failed. I tried a bunch of stuff to no avail. The solution was to simply get a new set of platform tools because mine was too old. Doesn't hurt to try.
Snorbro said:
I noticed something a while back when I attempted to flash recovery on a different phone (nexus 6) but failed. I tried a bunch of stuff to no avail. The solution was to simply get a new set of platform tools because mine was too old. Doesn't hurt to try.
Click to expand...
Click to collapse
Thank you for trying. I just found a post, (and now I can't find it), but the guy went through what I did, and then he used KingRoot, http://www.kingroot.net/ , and it worked.
So, I tried it too, and magic, it worked. I now have root and TWRP installed.
I could have sworn I tried KingRoot, but it must have been on another phone I had.
Are you sure your recovery file is called recovery.img and not twrp.xxx.img? If not you need to rename it
Another problem I had, I was using a USB 3.0 port on my computer. This is a not the way. Using a USB 2.0 port works on flashing stuff.
Hi faheyd, I also have XT1526 on android 5.0.2, but kingroot fails. I was told not to update OS to keep it working in India.
Doess ur phone run on 5.1?
Does USB debugging needs to be activated?
drshreenivaas said:
Hi faheyd, I also have XT1526 on android 5.0.2, but kingroot fails. I was told not to update OS to keep it working in India.
Doess ur phone run on 5.1?
Does USB debugging needs to be activated?
Click to expand...
Click to collapse
I have no idea, hopefully someone that knows will step in and help.
Hi,
i've a little (big?) problem with my xperia tablet z (wifi; pollux_windy). 2 years ago i've rooted the stock-rom (4.2 or 4.4) and installed dual-recovery. a while a did nothing with the tablet. later i installed cyanogenmod 11 using the installed recovery. someday in 2016 i updated to cyanogenmod 12, but i can remeber how i did this exactly - maybe with a update-app? after the update to cm 12 the dual-recovery was overwritten with a cyanogenmod-recovery.
i don't know whether the bootloader is unlocked. i've unlocked i to root the device for the first time. when i search for the imei in "about tablet / status / imei" there is only "unknown". so at the moment i can't unlock the bootloader again.
when i boot the device in fastboot mode and try to flash twrp with
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
i get this error
fastboot flash recovery twrp.img
sending 'recovery' (10688 KB)...
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.359s
Click to expand...
Click to collapse
maybe this is because the bootloader isn't unlocked anymore? how can i find out that? how can i unlock the bootloader again without the imei or how can i find out the imei?
a user in a german forum said i can use the sony tool emma, this should reset the tablet. but WHAT will emma reset? can i flash twrp after that? can i root it again?
pieremallao
From fastboot you have to type
fastboot flash boot twrp.img
Click to expand...
Click to collapse
what is the different between
Code:
fastboot flash recovery
and
Code:
fastboot flash boot
?
PiereMallao said:
what is the different between
Code:
fastboot flash recovery
and
Code:
fastboot flash boot
?
Click to expand...
Click to collapse
as far as I have understood they are two different partition, Sony devices have the recovery in the boot partition whereas other phones, such as my OnePlus One, have a dedicated partition.
But what I'm sure is that when I flashed TWRP in my OPO I used the "fastboot flash recovery twrp.img" but in my pollux_windy I had to use "fastboot flash boot twrp.img"
doesn't work. i tried this on ubuntu 16.04 and in terminal i see the message
Code:
sending 'boot' (10688 KB)...
since 30 minutes. maybe this is because the bootloader isn't unlocked? but i'm not sure about that? how can i check this?
I remember very well the code I entered to get TWRP, now I'm also thinking you have somehow a locked bootloader...
PiereMallao said:
how can i check this?
Click to expand...
Click to collapse
if you use a stock ROM try: contacts/press three dots/Settings/press a place above home knob for few sec/it will appear Enter service Code/type *#*#7378423#*#*/Service info/Configuration
no, i dont use a stock, i use cyzanogenmod 12. i dont have the contacts app on mz tablet installed. i have tried to install google apps but the cyanogen recovery cant install the gapps. can i tried the service codes with an other app?
PiereMallao said:
can i tried the service codes with an other app?
Click to expand...
Click to collapse
Try to download ExDialer - Dialer & Contacts and launch the code from there. I tried with it but it didn't work (probably because I'm on RR) so I doubt it will work for you but give it a try.
With the same app try
Code:
*#*#759#*#*
and I have "OEM mode = off" but I'm not sure if it means that your bootloader is unlocked.
Or download Secret codes, the app's icon is a magick stick with a star at the and it shows some codes and you can lauch them from the app itself. I think it only shows the codes available to your phone/tablet because it doesn't show 7378423.
-Pepe said:
Try to download ExDialer - Dialer & Contacts and launch the code from there. I tried with it but it didn't work (probably because I'm on RR) so I doubt it will work for you but give it a try.
Click to expand...
Click to collapse
On CM there is no service menu, so it won't work.
Unlocking is possible with Flashtool or fastboot commands.
deleted
Hi,
Last week I got my phone stuck in a bootloop which led to me making a lot of mistakes, I flashed a boot.img as a kernel, I deleted my entire software, and I lost a lot of files. I currently have my phone in an error mode, it says I have to update the system again. I have access to fastboot but I do not have access to twrp (flashing the recovery doesn't work).
Can anyone help me with this problem?
pim8181 said:
Hi,
Last week I got my phone stuck in a bootloop which led to me making a lot of mistakes, I flashed a boot.img as a kernel, I deleted my entire software, and I lost a lot of files. I currently have my phone in an error mode, it says I have to update the system again. I have access to fastboot but I do not have access to twrp (flashing the recovery doesn't work).
Can anyone help me with this problem?
Click to expand...
Click to collapse
Is a really fastboot mode or error mode?
If it is fastboot what you see, Phone unlocked and FRP unlock?
kilroystyx said:
Is a really fastboot mode or error mode?
If it is fastboot what you see, Phone unlocked and FRP unlock?
Click to expand...
Click to collapse
I can get in both fastboot and error mode, I think fastboot is the most useful. It says PHONE Unlocked and FRP unlocked.
pim8181 said:
I can get in both fastboot and error mode, I think fastboot is the most useful. It says PHONE Unlocked and FRP unlocked.
Click to expand...
Click to collapse
-Do you know exactly which files or partitions did you mess?
-What is your region code and build number?
If you don’t know run this command is fastboot mode => fastboot oem get-build-number
-Do you have a TWRP backup from your device?
kilroystyx said:
-Do you know exactly which files or partitions did you mess?
-What is your region code and build number?
If you don’t know run this command is fastboot mode => fastboot oem get-build-number
-Do you have a TWRP backup from your device?
Click to expand...
Click to collapse
I don't know for sure which parts I messed up, but I do know these thing: I don't have an OS installed, and my kernel is a boot.img.
I don't know my region number for sure, but according to this post: https://forum.xda-developers.com/8-lite/how-to/huawei-regional-codes-t3740473 it should be C432.
My build number is ANE-LX1 8.0.0.126 (C432) and I should have a TWRP backup on my sd card from the moment my phone was only bootlooping.
pim8181 said:
I don't know for sure which parts I messed up, but I do know these thing: I don't have an OS installed, and my kernel is a boot.img.
I don't know my region number for sure, but according to this post: https://forum.xda-developers.com/8-lite/how-to/huawei-regional-codes-t3740473 it should be C432.
My build number is ANE-LX1 8.0.0.126 (C432) and I should have a TWRP backup on my sd card from the moment my phone was only bootlooping.
Click to expand...
Click to collapse
Do you have currently TWRP installed?
-Boot in the TWRP recovery and restore your backup.
-If your backup don't have all partitions let me know and I'll send you what is missing.
If you currently don't have TWRP installed?
-Go to fastboot mode and flash this TWRP
If boot then should be ok.
If remains bootlooping then you can wipe cache and reboot
If remains bootlooping you can test flash B126 with HuRUpdater
kilroystyx said:
Do you have currently TWRP installed?
-Boot in the TWRP recovery and restore your backup.
-If your backup don't have all partitions let me know and I'll send you what is missing.
If you currently don't have TWRP installed?
-Go to fastboot mode and flash this TWRP
If boot then should be ok.
If remains bootlooping then you can wipe cache and reboot
If remains bootlooping you can test flash B126 with HuRUpdater
Click to expand...
Click to collapse
I can't install TWRP, I currently install it by flashing the file as a recovery_ramdisk.
After it is flashed I execute the command fastboot reboot and hold volume up whilst disconnecting my phone from my PC.
Do you have any tips?
pim8181 said:
I can't install TWRP, I currently install it by flashing the file as a recovery_ramdisk.
After it is flashed I execute the command fastboot reboot and hold volume up whilst disconnecting my phone from my PC.
Do you have any tips?
Click to expand...
Click to collapse
No, you are doing right. Can you post the output from fastboot during the installation?
kilroystyx said:
No, you are doing right. Can you post the output from fastboot during the installation?
Click to expand...
Click to collapse
Code:
fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
gives:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.689s]
writing 'recovery_ramdisk'...
OKAY [ 0.122s]
finished. total time: 0.811s
Since I can't boot in TWRP by holding down the volume up button when rebooting I tried to use the boot command:
Code:
fastboot boot TWRP_3.2.1-0_ANE-LX1_Full_01.img
downloading 'boot.img'...
OKAY [ 0.690s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.695s
pim8181 said:
Code:
fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
gives:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.689s]
writing 'recovery_ramdisk'...
OKAY [ 0.122s]
finished. total time: 0.811s
Since I can't boot in TWRP by holding down the volume up button when rebooting I tried to use the boot command:
Code:
fastboot boot TWRP_3.2.1-0_ANE-LX1_Full_01.img
downloading 'boot.img'...
OKAY [ 0.690s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.695s
Click to expand...
Click to collapse
I don't believe that fastboot boot can work...
That is strange...
Can you flash TWRP one more time?
After successful flash don't use the command fastboot reboot
Unplug the USB cable and press ON/OFF and VOL+ and stay pressings until you see TWRP screen.
kilroystyx said:
I don't believe that fastboot boot can work...
That is strange...
Can you flash TWRP one more time?
After successful flash don't use the command fastboot reboot
Unplug the USB cable and press ON/OFF and VOL+ and stay pressings until you see TWRP screen.
Click to expand...
Click to collapse
It didn't work , maybe I can flash the stock system image from fastboot?
pim8181 said:
It didn't work , maybe I can flash the stock system image from fastboot?
Click to expand...
Click to collapse
Yes, system, cust, recovery_ramdisk.... all partions that might be mess by you.
kilroystyx said:
Yes, system, cust, recovery_ramdisk.... all partions that might be mess by you.
Click to expand...
Click to collapse
I don't know how to get these ones can you explain it to me?
pim8181 said:
I don't know how to get these ones can you explain it to me?
Click to expand...
Click to collapse
Check this thread, this applies to recovery_ramdisk but for all other partitions is the same.
kilroystyx said:
Check this thread, this applies to recovery_ramdisk but for all other partitions is the same.
Click to expand...
Click to collapse
It worked, many thanks for your help!
For those that have issues with the programme, I had to uncheck the verify header checksum button in the settings file in order for it to work properly.
kilroystyx said:
Do you have currently TWRP installed?
-Boot in the TWRP recovery and restore your backup.
-If your backup don't have all partitions let me know and I'll send you what is missing.
If you currently don't have TWRP installed?
-Go to fastboot mode and flash this TWRP
If boot then should be ok.
If remains bootlooping then you can wipe cache and reboot
If remains bootlooping you can test flash B126 with HuRUpdater
Click to expand...
Click to collapse
I guess I spoke too soon, I can get my phone in TWRP but it continues to bootloop.
pim8181 said:
I guess I spoke too soon, I can get my phone in TWRP but it continues to bootloop.
Click to expand...
Click to collapse
Did you do wipes?
If didn't work use your TWRP backup or use HuRUpdater
kilroystyx said:
Did you do wipes?
If didn't work use your TWRP backup or use HuRUpdater
Click to expand...
Click to collapse
My TWRP is completely lost and the tool doesn't seem to work, I wiped data cache and dalvik.
When you flash a rom aren't you just supposed to flash the rom itself, when I bricked my phone by installing Xposed I just reflashed the rom it's sytem image and a boot image. How should I do it?
I'm trying to root my Pixel 3 and my device is stuck on the white google loading screen after flashing the patched boot file.
Here is what I've done so far:
Downloaded the boot image -> Installed Magisk on my phone -> patched the boot image -> booted into Fastboot -> flashed the patched boot image -> then my phone restarted and has been stuck on the white google loading screen.
If I hold the volume down button and the power button, my screen goes to the Fastboot mode. Then if I try to power off and start the phone, I get back to the white google loading screen which doesn't change.
Heres the logs from terminal if that provides any info:
(base) [email protected] android % ./fastboot flash boot magisk_patched.img
Sending 'boot_b' (31860 KB) OKAY [ 0.310s]
Writing 'boot_b' OKAY [ 0.258s]
Finished. Total time: 0.837s
(base) [email protected] android % ./fastboot reboot
Rebooting OKAY [ 0.080s]
Finished. Total time: 0.080s
Anyone have any ideas? everything was going smoothly until this point so not sure what I've done wrong. Any help is appreciated, thanks!
@MHuncho
Looks like the boot-loader got broken. Not unusal when flashing a system-less framework as Magisk. Probably dm-verity was enabled when you flashed Magisk's boot.img.
My advice: Try to re-flash Stock ROM.
jwoegerbauer said:
@MHuncho
Looks like the boot-loader got broken. Not unusal when flashing a system-less framework as Magisk.
Try to re-flash Stock ROM.
Click to expand...
Click to collapse
Thanks for the reply but slight issue. I got impatient and tried another solution which was:
(base) [email protected] android % ./fastboot flash boot --slot all magisk_patched.img
Sending 'boot_a' (31860 KB) OKAY [ 0.310s]
Writing 'boot_a' OKAY [ 0.494s]
Sending 'boot_b' (31860 KB) OKAY [ 0.200s]
Writing 'boot_b' OKAY [ 0.192s]
Finished. Total time: 1.760s
Now my device is stuck in a loop on the Fastboot Mode screen with following info:
Device state: unlocked
Boot slot: a
Enter Reason is: "no valid slot to boot'.
Also my device is now NOT recognised by my laptop so I'm unable to re-flash stock ROM as you suggested or do anything. sigh... I shouldn't have rushed.
@MHuncho
Congrats ... This is the price that people who think they must put up a better (?) ROM than that what gets pre-installed by OEM/Carrier - in their R&D department there are certainly no idiots sitting around - pay.
jwoegerbauer said:
@MHuncho
Congrats ... This is the price that people who think they must put up a better (?) ROM than that what gets pre-installed by OEM/Carrier - in their R&D department there are certainly no idiots sitting around - pay.
Click to expand...
Click to collapse
@jwoegerbauer
Slight success, after restarting my laptop, my device is now recognised but my devices is not found when I do ./adb devices and it is found when I do ./fastboot devices. Hence I'm unable to do the command ./adb reboot Bootloader and start the flashing stock ROM. I get the following when I do ./adb reboot Bootloader
(base) [email protected] android % ./adb reboot bootloader
error: no devices/emulators found
From research this may be because USB Debugging is not enabled? which I can't do because my device is stuck in fastboot.. ahh pls help
MHuncho said:
@jwoegerbauer
Slight success, after restarting my laptop, my device is now recognised but my devices is not found when I do ./adb devices and it is found when I do ./fastboot devices. Hence I'm unable to do the command ./adb reboot Bootloader and start the flashing stock ROM. I get the following when I do ./adb reboot Bootloader
(base) [email protected] android % ./adb reboot bootloader
error: no devices/emulators found
From research this may be because USB Debugging is not enabled? which I can't do because my device is stuck in fastboot.. ahh pls help
Click to expand...
Click to collapse
Hold power and volume down buttons to get to fastboot.
Tulsadiver said:
Hold power and volume down buttons to get to fastboot.
Click to expand...
Click to collapse
I'm already in fastboot, thats the only thing I can get to regardless of what I do the phone. Either completed off, or in fastboot
apparently I dont need ./adb to flash the factory image so I'll try just using fastboot
MHuncho said:
I'm already in fastboot, thats the only thing I can get to regardless of what I do the phone. Either completed off, or in fastboot
apparently I dont need ./adb to flash the factory image so I'll try just using fastboot
Click to expand...
Click to collapse
Unzip factory image zip and double click flash-all.bat. edit the flash-all.bat by taking off the -w if you don't want to delete data.
Tulsadiver said:
Unzip factory image zip and double click flash-all.bat. edit the flash-all.bat by taking off the -w if you don't want to delete data.
Click to expand...
Click to collapse
Would this work if I'm on a Mac? as its a bat file
MHuncho said:
Would this work if I'm on a Mac? as its a bat file
Click to expand...
Click to collapse
You should use the .sh file.
Tulsadiver said:
You should use the .sh file.
Click to expand...
Click to collapse
wooohoooo finally restored to factory image. I didn't use the .sh file as it was opening in notepad but got it working through terminal! thanks a lot!
I still want to root the phone again so how what would I need to change from my original post in this thread? as said @jwoegerbauer "better (?) ROM than that what gets pre-installed by OEM/Carrier" . does that mean I downloaded and patched the wrong boot image? hence why my phone was stuck in the white google loading screen for 1hour+?
MHuncho said:
wooohoooo finally restored to factory image. I didn't use the .sh file as it was opening in notepad but got it working through terminal! thanks a lot!
I still want to root the phone again so how what would I need to change from my original post in this thread? as said @jwoegerbauer "better (?) ROM than that what gets pre-installed by OEM/Carrier" . does that mean I downloaded and patched the wrong boot image? hence why my phone was stuck in the white google loading screen for 1hour+?
Click to expand...
Click to collapse
I believe that he was inferring that you are rooting in order to run a custom ROM and that maybe you should have stayed stock.
I don't know where you got your boot image but if you will unzip the image zip that was inside your firmware where you found the flash-all zips you should find the correct boot image to use. First you should enable developer settings and enable USB debugging so you can use USB. What you did sounded correct.