Related
Dear gurus of Android,
If possible I would like some help with my Galaxy Nexus since I think it is software bricked. When started it states the the phone is encrypted and wait for the key. I have read all I could get my hands on about this problem. No success so far, so I was hoping someone knowledgeable is willing to sacrifice some of his/her time to help me out.
Thanks in advance.
Hamal said:
Dear gurus of Android,
If possible I would like some help with my Galaxy Nexus since I think it is software bricked. When started it states the the phone is encrypted and wait for the key. I have read all I could get my hands on about this problem. No success so far, so I was hoping someone knowledgeable is willing to sacrifice some of his/her time to help me out.
Thanks in advance.
Click to expand...
Click to collapse
did you read this http://forum.xda-developers.com/showthread.php?t=1730463
Thanks for the quick response. Yes I did read the thread. It was one of the first things I tried. I lock/unlock the boot loader successfully. However when I start the phone in normal mode I get the same message, seems like nothing changed.
So no ideas ei. Seems Will be throwing away a perfectly functioning (hardware wise) Galaxy Nexus away. Shame since my other phone just died.
Anyway thanks for the effort.
Hamal said:
So no ideas ei. Seems Will be throwing away a perfectly functioning (hardware wise) Galaxy Nexus away. Shame since my other phone just died.
Anyway thanks for the effort.
Click to expand...
Click to collapse
Did you flashed factory image?
Sent from my Galaxy Nexus using xda app-developers app
razi914 said:
Did you flashed factory image?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I did, tried several, can't remember which Android version was that finally worked, however upon flashing after I started in normal mode the same **** - encrypted again like nothing happened.
What about CM or another rom?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
sui785 said:
What about CM or another rom?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well I only tried stock Android since this is what I really wanted. But does it make sense to try CM if stock does not work. IS there a chance CM works. IF you say I should try than I should I guess. Never thought about it. Thanks for the advice.
Did you flash the factory images with fastboot?
Returning to stock using this method http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1 may fix your problem.
jaizero said:
Did you flash the factory images with fastboot?
Returning to stock using this method http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1 may fix your problem.
Click to expand...
Click to collapse
Well I might be confusing the terms, but I think I did use fastboot. I got the command lines from the XDA Forum actually and entered them manually through the sdk console the way I remember it. I think I also used some-kind of automated tool that basically does the same. The result being the same naturally. But should it even matter. I mean the problem is that whatever I do once I start the phone in normal operation mode I get the encrypted storage message. I have no idea how to get around this. Should I not be able to completely wipe it somehow so there is nothing when I start it ?
Hamal said:
Well I might be confusing the terms, but I think I did use fastboot. I got the command lines from the XDA Forum actually and entered them manually through the sdk console the way I remember it. I think I also used some-kind of automated tool that basically does the same. The result being the same naturally. But should it even matter. I mean the problem is that whatever I do once I start the phone in normal operation mode I get the encrypted storage message. I have no idea how to get around this. Should I not be able to completely wipe it somehow so there is nothing when I start it ?
Click to expand...
Click to collapse
Can you get into the bootloader by pressing the volume up/down keys and power button? Does it give you the encrypted message there?
Were these the commands you used?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Optional (NOT optional for n00bs) -- Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot (not required if you did not do step 5): fastboot reboot-bootloader
7) Optional (NOT optional for n00bs) -- Flash the radio: fastboot flash radio radio-maguro-i9250xxla02.img (or whatever the name is of the radio image that you downloaded).
8) Reboot (not required if you did not do step 7): fastboot reboot-bootloader
8a) Verizon and Sprint devices only -- flash the LTE radio: fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img (or whatever the name is of the radio image that you downloaded).
8b) Verizon and Sprint devices only -- reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 5 below for optional items.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Optional (NOT optional for n00bs) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
15) Reboot: fastboot reboot
16) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
jaizero said:
Did you flash the factory images with fastboot?
Returning to stock using this method http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1 may fix your problem.
Click to expand...
Click to collapse
Jaizero I just did what you suggested. Followed the link you provided and did everything according to he procedure. There were no errors. However when I restarted the phone with the last command line and it booted up in normal mode there was the same message.
The screen looks like the one on the link below (not actually my phones, have no other one to make a picture with).
http://bensullins.com/wp-content/uploads/2011/12/Nexus-S-Decrypt-On-Reboot-Android-4-600x800.png
Also I do not know if it is relevant or not but when it boots the initial screen with the Google logo in the very beginning there is a closed lock icon below the Google logo, probably because of the encryption ?
Thanks for the help in advance again guys/girls.
jaizero said:
Can you get into the bootloader by pressing the volume up/down keys and power button? Does it give you the encrypted message there?
Were these the commands you used?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Optional (NOT optional for n00bs) -- Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot (not required if you did not do step 5): fastboot reboot-bootloader
7) Optional (NOT optional for n00bs) -- Flash the radio: fastboot flash radio radio-maguro-i9250xxla02.img (or whatever the name is of the radio image that you downloaded).
8) Reboot (not required if you did not do step 7): fastboot reboot-bootloader
8a) Verizon and Sprint devices only -- flash the LTE radio: fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img (or whatever the name is of the radio image that you downloaded).
8b) Verizon and Sprint devices only -- reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 5 below for optional items.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Optional (NOT optional for n00bs) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
15) Reboot: fastboot reboot
16) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Click to expand...
Click to collapse
Sorry saw your reply a bit too late. Yes these are the exact commands I used. Followed them exactly as stated every step worked out perfectly.
And no there is no encryption messaging while I am in the bootloader mode.
Hum... no replies. Seems like I am doing everything right yet results are bad. Means I am not doing everything right ofcourse. I am just not knowledgeable enough I guess to figure it out on my own.
Shame I really like the phone.
Hamal said:
Hum... no replies. Seems like I am doing everything right yet results are bad. Means I am not doing everything right ofcourse. I am just not knowledgeable enough I guess to figure it out on my own.
Shame I really like the phone.
Click to expand...
Click to collapse
Unlock the bootloader again, either through fastboot or omapflash. Did you try formatting partitions before flashing? Fastboot allows you to do that. Idk if you tried or have reserves towards ODIN, be extra careful both with omapflash and Odin. There's a link on unlocking the bootloader with omapflash on efrant's android 101 - links section, which is stickied on general.
a manta wrote this.
beekay201 said:
Unlock the bootloader again, either through fastboot or omapflash. Did you try formatting partitions before flashing? Fastboot allows you to do that. Idk if you tried or have reserves towards ODIN, be extra careful both with omapflash and Odin. There's a link on unlocking the bootloader with omapflash on efrant's android 101 - links section, which is stickied on general.
a manta wrote this.
Click to expand...
Click to collapse
Locking/Unlocking the bootloader does not work tried it a couple of times already. Will try the rest of what you suggested and let you know how it goes.
Thank you for the advice.
beekay201 said:
Unlock the bootloader again, either through fastboot or omapflash. Did you try formatting partitions before flashing? Fastboot allows you to do that. Idk if you tried or have reserves towards ODIN, be extra careful both with omapflash and Odin. There's a link on unlocking the bootloader with omapflash on efrant's android 101 - links section, which is stickied on general.
a manta wrote this.
Click to expand...
Click to collapse
I looked around the forums, could not find this Android 101 link tough. Any chance you might help me find it. I know I sound lazy but I really can't find the thread. Also I was thinking could an USB Jig solve this problem ?
If all else fails you could try this...
http://www.extremetech.com/computin...encryption-and-security-put-it-in-the-freezer
https://www1.informatik.uni-erlangen.de/frost
I don't see why fastboot erase userdata wouldn't work...
Sdobron said:
I don't see why fastboot erase userdata wouldn't work...
Click to expand...
Click to collapse
Well I did try it. What I did might be wrong, but here it is:
I followed the guide by jaizero for flashing via fastboot, but instead inserted " fastboot erase userdata" before the "fastboot flash userdata userdata.img" line. Than there was an error message on the phone, not on the pc command line screen, but it was so quick that I could not read it. However the process continued and was okay according to the command window and everyting went on as normal. Alas to no vail since the result was the same.
Any ideas ?
Ah I also noticed than in fastboot mode it said HW Version: 9. Any idea what it means ?
Thanks in advance for taking the time to bother with my bull
" SOLVED - System was using 19.99 gb's required user data format. " Cant flash any of 3 factory images ? Anyone have a clue why ? I have a verizon pixel Xl with unlocked bootloader rooted with the newest supersu and every time I try to flash any of the three factory images for pixel XL my adb tools gives me the error " error: failed to load 'image-marlin-nde63l.zip': Not enough space " I flashed images just fine a couple weeks ago on both my Nexus 6 and my Nexus 9 but for some reason I keep getting this problem.
I have tried using flash-all.bat and that is what I get. I never have had any luck using flash-all.bat in the past with my Nexus 6 & 9 so I would use the manual method which I"am listing below but there are a lot more things to flash on these pixel XL. So hopefully someone can list how to manually flash an image on the pixel XL because its totally different. Hopefully someone can tell me what is the problem ?
Run fastboot commands
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Add next step for Nexus 9
fastboot flash vendor vendor.img
I have also tried the following steps and on the last step flashing the image I still get " error: failed to load 'image-marlin-nde63l.zip': Not enough space "
Steps I tried are:
fastboot flash bootloader bootloader-marlin-8996-012001-1608281716.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012511-1609150631.img
fastboot reboot-bootloader
fastboot -w update image-marlin-nde63l.zip
I just checked my setting and I have 19.99 gb's used by the system. That seems way too much. Could that be the problem ?
M9guy said:
I just checked my setting and I have 19.99 gb's used by the system. That seems way too much. Could that be the problem ?
Click to expand...
Click to collapse
Yeah sounds like it to me might have to wipe userdata that will wipe your phone completely
When I flash the images I use the flash-all.sh.
This works for me "sudo sh flash-all.sh"
I had same issue. I have sideloaded the update zip temporarily. I still wonder what's wrong in flashing zip file. I dont think its the issue with size because i had almost 90GB space left.
M9guy said:
I just checked my setting and I have 19.99 gb's used by the system. That seems way too much. Could that be the problem ?
Click to expand...
Click to collapse
When I flash the images I use the flash-all.sh.
This works for me "sudo sh flash-all.sh"
M9guy said:
I have a verizon pixel Xl with unlocked bootloader rooted with the newest supersu and every time I try to flash any of the three factory images for pixel XL my adb tools gives me the error " error: failed to load 'image-marlin-nde63l.zip': Not enough space "
Click to expand...
Click to collapse
You don't use ADB to flash factory image. You use fastboot, from your bootloader...
cam30era said:
You don't use ADB to flash factory image. You use fastboot, from your bootloader...
Click to expand...
Click to collapse
I was in bootloader fastboot mode and i saw same issue.
rootSr. said:
I was in bootloader fastboot mode and i saw same issue.
Click to expand...
Click to collapse
Just to confirm, you unzipped the factory image and did: fastboot flash system system.img?
If so, you might need to update your Android SDK...
cam30era said:
You don't use ADB to flash factory image. You use fastboot, from your bootloader...
Click to expand...
Click to collapse
I put phone in bootloader mode and held down shift button and righted clicked on my folder with my adb tool that I extracted all files to.
http://androiding.how/flash-firmware-factory-image-google-pixel/
jaythenut said:
Yeah sounds like it to me might have to wipe userdata that will wipe your phone completely
Click to expand...
Click to collapse
The method at the link below I had tried it previously and it did format my data but now each time I boot the phone I get " There"s an internal problem with your device. Contact your manufacturer for details. "
http://androiding.how/flash-firmware-factory-image-google-pixel/
zaksimmermon said:
When I flash the images I use the flash-all.sh.
This works for me "sudo sh flash-all.sh"
Click to expand...
Click to collapse
I have windows 10, which for windows your supposed to use flash-all.bat which that gave me the same error on the last step flashing the system image.
rootSr. said:
I had same issue. I have sideloaded the update zip temporarily. I still wonder what's wrong in flashing zip file. I dont think its the issue with size because i had almost 90GB space left.
Click to expand...
Click to collapse
I have the update downloaded to the phone it just wont install it think because I was rooted, even after formatting user data starting over it still would not install the update with no supersu installed.
Do you remember where the update was downloaded to on your phone what folder, or did you download the update somewhere else to your computer ?
cam30era said:
Just to confirm, you unzipped the factory image and did: fastboot flash system system.img?
If so, you might need to update your Android SDK...
Click to expand...
Click to collapse
It makes sense, I will update and verify. Thanks for quick reply Cam
rootSr. said:
It makes sense, I will update and verify. Thanks for quick reply Cam
Click to expand...
Click to collapse
I just tried updating my Minimal ADB and Fastboot [10-22-16] and still same error. I thought I had already updated but I tried again anyway and still no go, and that was updated on 10-22-16
http://forum.xda-developers.com/showthread.php?t=2317790
M9guy said:
I have windows 10, which for windows your supposed to use flash-all.bat which that gave me the same error on the last step flashing the system image.
Click to expand...
Click to collapse
What version is your pixel running now? I'm on NDE63P.
zaksimmermon said:
What version is your pixel running now? I'm on NDE63P.
Click to expand...
Click to collapse
I"am on NDE63L
You need to try updating the SDK through the SDK manager. It'll have a box to check of to update SDK 25.
Sent from my Pixel XL using Tapatalk
rootSr. said:
It makes sense, I will update and verify. Thanks for quick reply Cam
Click to expand...
Click to collapse
It did work without any issues. I have cleared old SDK and downloaded new. Worked flawless. Thanks. :good:
So I tried to flash another rom by flashing TWRP and unlocking the bootloader, which worked and I then had installed Freedom Os. Then I locked the Bootloader to get the Message away, but know when you charge it or turn it on it is in an boot loop which repeats the Oneplus Logo what you normally see, but very short and after that it bobrates turns the screen off and it atart again. Or I can go into fastboot mode, but when I try to go into the recovery, it goes into the Boot Loop again. Is there a way to get the Original OS back? Ive already dopwnloaded it but I cant get in on there. Can you tell me how to fix it on my own?
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3 > METHOD 1
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
anup807 said:
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
Click to expand...
Click to collapse
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
revedar said:
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
Click to expand...
Click to collapse
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
anup807 said:
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
Click to expand...
Click to collapse
So i've downloaded the software, installed the driver and typed in cmd adb devices "adb devices List of devices attached" is returned, so it seems like there is going something wrong. Is it because the Driver is installed wrong or because "target reported max download size of 440401920 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.528s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.551s"
This is returned when trying to flash. Do I have to be in fastboot mode or something else to be able to follow your instructions? In Fast Boot is written that the Device State is locked and Secure Boot is enabled. I messaged Oneplus and hope they have a solution which can just unlock the Bootloader when being in fastboot mode, so everything is fine again. I hope you can help me, but I still wanna say thank your for now
Errr... fastboot can unlock the bootloader. fastboot oem unlock
emuandco said:
Errr... fastboot can unlock the bootloader. fastboot oem unlock
Click to expand...
Click to collapse
Thank you, but it dont works because i forgot to re-enable the oem modification and usb debugging in freedom os, maybe there is an option to do this without having this enabled but I didnt found it. So I wait for a helpful answer from somebody here or from Oneplus, I consider sending my smartphone to oneplus to let them repair it if I cant do it. Just saying that modding an S3, Asus transformer pad and nvidia shield is way easier.
never ever relock your bootloader while you in custom OS
oopstairs said:
never ever relock your bootloader while you in custom OS
Click to expand...
Click to collapse
Thank you for not helping me
revedar said:
Thank you for not helping me
Click to expand...
Click to collapse
Yeah I'm sorry I can't help you in your case. I'm just stating the fact. Sorry if I offended you.
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
emuandco said:
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Click to expand...
Click to collapse
I already tried to do this, but the console returns something like permission denied.
anup807 said:
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
Click to expand...
Click to collapse
The MSM Software disconnects the smartphone while the process works
U cannot flash in adb while the bootloader is locked, u can not unlock the bootloader unless u can access ur OS, I am not sure y people was trying to get u to flash via fastboot the answer was provided to u in the 2nd post
^^^ This!
It's pretty much obvious fastboot flash will not work with a locked bootloader.
It's pretty obvious unlocking the bootloader will not work, while one can not access the OS.
Unbrick tool is the only option to bring it back to life, or sending it for RMA. If unbrick tool fails, try using different drivers and make sure it is connected with the stock cable (I've only tried with a Nilkin cable besides the stock one, which always failed at different stages during the process).
Not even sure drivers must be installed manually, I've never done that myself on Windows 10, as they were automatically installed (3 different's PC's, both on x86 and x64).
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
rk2612 said:
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
Click to expand...
Click to collapse
I had the most recent update installed. Is there a similar command at the moment?
revedar said:
I had the most recent update installed. Is there a similar command at the moment?
Click to expand...
Click to collapse
Don't think so.
I was following the steps on the rooting process with twrp and I got twrp to boot but i couldn't boot into the system and now it's just stuck in download mode is there any way to fix it
Djcall11 said:
I was following the steps on the rooting process with twrp and I got twrp to boot but i couldn't boot into the system and now it's just stuck in download mode is there any way to fix it
Click to expand...
Click to collapse
Download the factory images.
Run flasg_all.bat.
If you dont want your data partition to be formatted, then edit the .bat file and remove the line where it says "erase userdata". You can also remove tge last line that reads "fastboot reboot".
When rooting, i always boot into twrp using the image and flash both twrp zip and magisk zip in one go.
iliais347 said:
Download the factory images.
Run flasg_all.bat.
If you dont want your data partition to be formatted, then edit the .bat file and remove the line where it says "erase userdata". You can also remove tge last line that reads "fastboot reboot".
When rooting, i always boot into twrp using the image and flash both twrp zip and magisk zip in one go.
Click to expand...
Click to collapse
i have to edit the bat file and add -i 0x1532 to every command anyway for the command to work
so... the razer loading green effect is happening but it hasn't passed that it just keeps going
should I just put back the command to delete the user data
Have you unlocked the critical portion of the bootloader? (First thing I always ask)
If yes then yeah just wipe the whole thing.
Roxas598 said:
Have you unlocked the critical portion of the bootloader? (First thing I always ask)
If yes then yeah just wipe the whole thing.
Click to expand...
Click to collapse
welp the phone booted but it just stays on the loading screen and when I restart it just goes straight to download mode
I did unlock_critical and it just tells me that the device is already unlocked
I don't really know what else I can do from here
Of both bootloader portions are unlocked it should just be a case of running the flash all script from the factory images and you're good to go :S only other thing I can suggest to make sure there's nothing bad in there and in fastboot wiping user data again.
Roxas598 said:
Of both bootloader portions are unlocked it should just be a case of running the flash all script from the factory images and you're good to go :S only other thing I can suggest to make sure there's nothing bad in there and in fastboot wiping user data again.
Click to expand...
Click to collapse
I ran the script how it was and I just get stuck at the green effect loading I will try some other commands and I'm about to try the 7.1.1 mr3 rom to see if that work
so using the 7.1.1 mr3 worked i finally have my phone back thank guy for the help
Djcall11 said:
i have to edit the bat file and add -i 0x1532 to every command anyway for the command to work
Click to expand...
Click to collapse
Why is that? I didnt have to do that.
What does that command do?
Stuck on boot logo !!!!! :crying:
Can't :
1. Can't boot to ROM (as doing so just stays on boot logo)
2. Can't boot into recovery (as doing this gets me to either black screen or just boots back to the boot logo)
Can :
1. Can enter bootloader
2. Can able to use fastboot commands
Tried:
1. flashing stock ROM several times,
2. flashing stock recovery
3. flashing twrp recovery
:crying:
Check my guide. It might come handy.
https://forum.xda-developers.com/le...-lenovo-p2-t4006405/post80955105#post80955105
alirazaagha said:
Check my guide. It might come handy.
https://forum.xda-developers.com/le...-lenovo-p2-t4006405/post80955105#post80955105
Click to expand...
Click to collapse
Friend thanks for the reply but your link just says "Duplicate thread. "
hackiee said:
Friend thanks for the reply but your link just says "Duplicate thread. "
Click to expand...
Click to collapse
Yes, it was. Check this one.
https://forum.xda-developers.com/lenovo-p2/how-to/guide-unbrick-unlocked-lenovo-p2-t4006401
alirazaagha said:
Yes, it was. Check this one.
https://forum.xda-developers.com/lenovo-p2/how-to/guide-unbrick-unlocked-lenovo-p2-t4006401
Click to expand...
Click to collapse
Thanks for your post friend, but, your guide doesn't fulfill my situation.
As, I am stuck on bootliader or boot logo.
I have flashed all firmwares s048,s233,s244,s51 through fastboot but none of them able to get me out of it.
Even tried flashing various recoveries both stock and twrp but neither of them helped
If, anyhow I can be able to enter into TWRP. It will solve the problem. But, I don't know nothing seems to work.
Even tried corrupting the bootloader and then flashing blankflash, but that too didn't able to get me out of the bootlogo.
Please help ?
alirazaagha said:
Yes, it was. Check this one.
https://forum.xda-developers.com/lenovo-p2/how-to/guide-unbrick-unlocked-lenovo-p2-t4006401
Click to expand...
Click to collapse
Hey, can you please do 1 thing.
Can you provide an image of the bootloader mode of your lenovo p2, if, there's something to lookup idk
I am attaching image of my bootloader, if you can look into it.
Thanks
hackiee said:
Hey, can you please do 1 thing.
Can you provide an image of the bootloader mode of your lenovo p2, if, there's something to lookup idk
I am attaching image of my bootloader, if you can look into it.
Thanks
Click to expand...
Click to collapse
It's alright.
alirazaagha said:
It's alright.
Click to expand...
Click to collapse
nothing strange ? Ok thanks
hackiee said:
nothing strange ? Ok thanks
Click to expand...
Click to collapse
Yep. Go ahead. You can try S244 firmware to try and boot your phone. If it boots then update accordingly as I mentioned in my guide.
alirazaagha said:
Yep. Go ahead. You can try S244 firmware to try and boot your phone. If it boots then update accordingly as I mentioned in my guide.
Click to expand...
Click to collapse
Still no luck! :crying: flashed S244 several times but nothing.
Can you confirm one more thing.
When I give
"Fastboot format system" I get :
"Formatting is not supported for file system with type 'raw'."
screenshot attached. Please check
hackiee said:
Still no luck! :crying: flashed S244 several times but nothing.
Can you confirm one more thing.
When I give
"Fastboot format system" I get :
"Formatting is not supported for file system with type 'raw'."
screenshot attached. Please check
Click to expand...
Click to collapse
OK so you are not following my guide Check .txt file attached in that guide and if you are still unsure then ask me.
alirazaagha said:
OK so you are not following my guide Check .txt file attached in that guide and if you are still unsure then ask me.
Click to expand...
Click to collapse
I have checked the text file of your guide, and they are the same instructions which I have been following since start. :silly:
The "fastboot format system" is a command which I used to do on my Moto G, and was able to format system successfully.
But, I don't remember if it used to work on P2 or not , that's why I asked you. If, you can use that command to check the output on your device.
Thanks
hackiee said:
I have checked the text file of your guide, and they are the same instructions which I have been following since start. :silly:
The "fastboot format system" is a command which I used to do on my Moto G, and was able to format system successfully.
But, I don't remember if it used to work on P2 or not , that's why I asked you. If, you can use that command to check the output on your device.
Thanks
Click to expand...
Click to collapse
Hmmm so you haven't read .txt file carefully. Command is:
Fastboot ERASE system
See the difference now? :silly:
Please, discuss it on that thread if need so others could also benefit from it.
alirazaagha said:
Hmmm so you haven't read .txt file carefully. Command is:
Fastboot ERASE system.
Click to expand...
Click to collapse
OMG, yes brother, I already know the command, and I have used it several times, the fastboot ERASE command, but, as mentioned several timesin the past, it is not solving my problem.
As, I am still not able to enter into any recovery(neither stock nor twrp), and not able to boot and OS.
That's why, I wanna try "Fastboot format system" command.
If, somehow that solves my problem
hackiee said:
OMG, yes brother, I already know the command, and I have used it several times, the fastboot ERASE command, but, as mentioned several timesin the past, it is not solving my problem.
As, I am still not able to enter into any recovery(neither stock nor twrp), and not able to boot and OS.
That's why, I wanna try "Fastboot format system" command.
If, somehow that solves my problem
Click to expand...
Click to collapse
OK. I though that you only tried Format command not erase. You should skip this command and do the whole process. I have added this command so that previous system files are erased. But, I booted my phone without using this command first time. Second time, I tried to see if I can do it all in a single process then I added this command and it worked without any issues and all the process went smooth and phone booted like a new one.
Try all commands but skip erase system command.
stuck on logo , have access to fastboot only
My phone stuck on logo when i open it or when i insert charger
when i try to open recovery(volume up + down) it turned off and i can't open recovery by any way
i can access fastboot
i tried your instruction and Lenovo+P2+UnBrick+OneTeam-EypCnn and all other fastboot roms
i tried install Twrp and stock recovery
i tried blankflash
that didn't help ,i can only access fastboot
what is your recommendation ? it's a hardware issue ?
DrGhost001 said:
stuck on logo , have access to fastboot only
My phone stuck on logo when i open it or when i insert charger
when i try to open recovery(volume up + down) it turned off and i can't open recovery by any way
i can access fastboot
i tried your instruction and Lenovo+P2+UnBrick+OneTeam-EypCnn and all other fastboot roms
i tried install Twrp and stock recovery
i tried blankflash
that didn't help ,i can only access fastboot
what is your recommendation ? it's a hardware issue ?
Click to expand...
Click to collapse
Did you find any solution?
Same issue here, I guess it's a hardware issue: SSD is damaged ?
fastboot erase system
fastboot format:ext4 system
Maybe related to the file system ?
i have the same probelm, do you guys find any solution ?