Related
I know this topic is not popular and most people may skip over it but please read. I am NO expert when it comes to this so if anybody can help out it would be most appreciated. I have a T-mobile My touch 4g( NOT the slide version) running ginger bread 2.3.4. I wanted to play a game called "Clash of clans" but it says i need firmware 4.1 or higher. I was bummed because T mobile stopped making upgrades for this phone a long time ago. I saw online from different threads and videos that I need to downgrade the firmware and go back to fre3vo 2.2. OK i'm fine with that. I had no Idea how adb worked so I saw a post on xda this site how to use it for dummies. I now know how to. I followed ALL steps from http://forum.xda-developers.com/showthread.php?t=1178912 on how I should go about this process. Everything went smooth up until the "Downgrading steps." I finally learned how to place the zip file named "PD15IMG.zip" in the root of sd card. Ok i had it. I also followed the manual downgrade routine. The phone went into boot-loader mode. The phone scanned the file and that took maybe 2 min before it asked me to update. I hit yes to update. I waited for the phone to update then it shut off. I guess the phone restarted to a black screen. The only thing I could see was the top portion bar where the battery and time info is. The rest of the screen was completely black. I took the battery out thinking that maybe the phone just needed to be restarted and this was the worst thing to happen. I turned the phone on and now the screen will NOT boot past the "t mobile mytouch 4g logo screen. I have no idea what to do from here. I went to go back to clockworkmod to see if i could repeat the process. The package scans like before then it asks me to update then I said yes. This is where the phone says its "updating" in pink letter on the side but NO progress is being made. Nothing happens and the phone seems unresponsive. I took the battery out and went back to clockworkmod. I tried to hit 'Factory Reset' but it just stays highlighted on factory reset and it wont move up and down. Nothing works. I took the battery out and re tried clockworkmod. I tried hitting recovery and then a "phone with a "green arrow" below shows up then the screen goes black and the phone vibrates 7 times then nothing else happens. I can no longer access the phone on my computer. Normally when I plugged it in the F: drive folder came up indicating I could change contents in the Sd card. I heard that you can change the setting using terminal and when i try typing "adb shell" it said it cannot find my phone and that my phone inst connected although it is connected to my computer. I have windows 7 Toshiba satellite so nothing is bad on the PC. Battery, cable, everything is fine no defects with the phone.
Also
A little information when ClockWorkMod is up. This is exactly what it says and this is exactly the color as it shows.
GLACIER PUT SHIP S-ON
HBOOT-0.89.0005
MICROP-0429
RADIO-26.11.04.03_M
eMMC-boot
Apr 14 2011, 13;18;22
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Since I can no longer access the phone on my pc I took the micro sim sd out and placed it in my samsung galaxy player 3.6 From there I can at least change what goes into the Sd card. I have searched countless hours and nothing else comes up. I CANNOT go back to the normal mode my phone used to be. I just freezes past mytouch4g screen. Please help anybody. I want to downgrade ginger bread 2.3.4 to fre3vo 2.2 so i can root and upgrade to jelly bean or something higher to play clash of clans since this phone wasn't compatable. Please somebody help. Can I ever use my phone again? Does this mean it's bricked? I'm an apple user so I have little experience with android. Somebody anybody help me out?
Here are a few links i used in the process
http://lifehacker.com/5853519/how-do-i-fix-my-bricked-android-phone
http://forum.xda-developers.com/showthread.php?t=863899
help me please
Bolt34 said:
I know this topic is not popular and most people may skip over it but please read. I am NO expert when it comes to this so if anybody can help out it would be most appreciated. I have a T-mobile My touch 4g( NOT the slide version) running ginger bread 2.3.4. I wanted to play a game called "Clash of clans" but it says i need firmware 4.1 or higher. I was bummed because T mobile stopped making upgrades for this phone a long time ago. I saw online from different threads and videos that I need to downgrade the firmware and go back to fre3vo 2.2. OK i'm fine with that. I had no Idea how adb worked so I saw a post on xda this site how to use it for dummies. I now know how to. I followed ALL steps from http://forum.xda-developers.com/showthread.php?t=1178912 on how I should go about this process. Everything went smooth up until the "Downgrading steps." I finally learned how to place the zip file named "PD15IMG.zip" in the root of sd card. Ok i had it. I also followed the manual downgrade routine. The phone went into boot-loader mode. The phone scanned the file and that took maybe 2 min before it asked me to update. I hit yes to update. I waited for the phone to update then it shut off. I guess the phone restarted to a black screen. The only thing I could see was the top portion bar where the battery and time info is. The rest of the screen was completely black. I took the battery out thinking that maybe the phone just needed to be restarted and this was the worst thing to happen. I turned the phone on and now the screen will NOT boot past the "t mobile mytouch 4g logo screen. I have no idea what to do from here. I went to go back to clockworkmod to see if i could repeat the process. The package scans like before then it asks me to update then I said yes. This is where the phone says its "updating" in pink letter on the side but NO progress is being made. Nothing happens and the phone seems unresponsive. I took the battery out and went back to clockworkmod. I tried to hit 'Factory Reset' but it just stays highlighted on factory reset and it wont move up and down. Nothing works. I took the battery out and re tried clockworkmod. I tried hitting recovery and then a "phone with a "green arrow" below shows up then the screen goes black and the phone vibrates 7 times then nothing else happens. I can no longer access the phone on my computer. Normally when I plugged it in the F: drive folder came up indicating I could change contents in the Sd card. I heard that you can change the setting using terminal and when i try typing "adb shell" it said it cannot find my phone and that my phone inst connected although it is connected to my computer. I have windows 7 Toshiba satellite so nothing is bad on the PC. Battery, cable, everything is fine no defects with the phone.
Also
A little information when ClockWorkMod is up. This is exactly what it says and this is exactly the color as it shows.
GLACIER PUT SHIP S-ON
HBOOT-0.89.0005
MICROP-0429
RADIO-26.11.04.03_M
eMMC-boot
Apr 14 2011, 13;18;22
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Since I can no longer access the phone on my pc I took the micro sim sd out and placed it in my samsung galaxy player 3.6 From there I can at least change what goes into the Sd card. I have searched countless hours and nothing else comes up. I CANNOT go back to the normal mode my phone used to be. I just freezes past mytouch4g screen. Please help anybody. I want to downgrade ginger bread 2.3.4 to fre3vo 2.2 so i can root and upgrade to jelly bean or something higher to play clash of clans since this phone wasn't compatable. Please somebody help. Can I ever use my phone again? Does this mean it's bricked? I'm an apple user so I have little experience with android. Somebody anybody help me out?
Here are a few links i used in the process
http://lifehacker.com/5853519/how-do-i-fix-my-bricked-android-phone
http://forum.xda-developers.com/showthread.php?t=863899
help me please
Click to expand...
Click to collapse
Bro calm down. I've been though panic attacks like this too lol
Open clockworkmod
To select or scroll use the TRACKPAD
Put a rom on your sdcard, find any in the resource bible in the development section
Do a factory reset and flash that rom
And yay,
N_otori0us_ said:
Bro calm down. I've been though panic attacks like this too lol
Open clockworkmod
To select or scroll use the TRACKPAD
Put a rom on your sdcard, find any in the resource bible in the development section
Do a factory reset and flash that rom
And yay,
Click to expand...
Click to collapse
-It won't allow me to use the track pad I can only use the volume up and down buttons to scroll. What rom should I put on my sd card? If you have a link or something that would be great.. Also when I try to factory reset the phone just freezes. I don't know what to do.
any rom
That screen you posted information from is called H-BOOT, it's like the factory boot loader. Clockwork MOD will show up after that but from what I'm gathering you didn't even install that in the first place. In H-BOOT you can only use the volume buttons and the power button to select so that is all normal.
So you downloaded the stock ROM and in the process of downgrading got stuck. If the SD card still works in other devices do you still have PD15IMG.zip on the card?
Also did you make sure to download the proper drivers for ADB and also for your phone? The ADB ones you should be able to find on this forum and the HTC ones you could get directly from you carriers website, and most likely somewhere on this forum. It will be up to you to really read, read, read, but I don't mind point you in the right direction.
You will find links of information with in this post http://forum.xda-developers.com/showthread.php?t=2288189
I would read through s-off / s-on and true rooting. I feel like you're missing drivers and basically just have nothing installed on the phone. So you aren't bricked, you just need to do more research. Bricked is the phone shows no screen at all and won't even turn on. I've done it once, and you are luckily not there. I believe the first time I rooted this phone I had the same problem of "is it installing...did I miss something...eff it, battery pull...oh no!"
Also select the recovery option and let me know what happens, if it advances you to the next screen that is what is actually Clockwork Mod recovery. If you actually have that then we are even better. I'll keep checking back tonight for ya.
tonyMEGAphone said:
That screen you posted information from is called H-BOOT, it's like the factory boot loader. Clockwork MOD will show up after that but from what I'm gathering you didn't even install that in the first place. In H-BOOT you can only use the volume buttons and the power button to select so that is all normal.
So you downloaded the stock ROM and in the process of downgrading got stuck. If the SD card still works in other devices do you still have PD15IMG.zip on the card?
Also did you make sure to download the proper drivers for ADB and also for your phone? The ADB ones you should be able to find on this forum and the HTC ones you could get directly from you carriers website, and most likely somewhere on this forum. It will be up to you to really read, read, read, but I don't mind point you in the right direction.
You will find links of information with in this post http://forum.xda-developers.com/showthread.php?t=2288189
I would read through s-off / s-on and true rooting. I feel like you're missing drivers and basically just have nothing installed on the phone. So you aren't bricked, you just need to do more research. Bricked is the phone shows no screen at all and won't even turn on. I've done it once, and you are luckily not there. I believe the first time I rooted this phone I had the same problem of "is it installing...did I miss something...eff it, battery pull...oh no!"
Also select the recovery option and let me know what happens, if it advances you to the next screen that is what is actually Clockwork Mod recovery. If you actually have that then we are even better. I'll keep checking back tonight for ya.
Click to expand...
Click to collapse
I appreciate the comment and help. Sorry i didn't know that I wasnt in colckworkmod just yet. Im new to android as I am an apple person. Some of the links i've found on this site are outdated or used by sites that are no longer running. If possible could you help direct me to the appropriate link so that I can download the correct rom? thank you so much!
first
First in your Hboot screen scroll with the volume button to "Recovery" and let me know what happens.
---------- Post added at 04:36 PM ---------- Previous post was at 04:29 PM ----------
Also did you go to tmobile and install the HTC drivers under the support menu for your phone?
These are all must I read through your post and also am currently reading the link you said you followed but if you didn't do all these prerequisite work it's no wonder why you froze up.
---------- Post added at 04:52 PM ---------- Previous post was at 04:36 PM ----------
I see, you said the Recovery goes black and vibrates 7 times. Something didn't install right. At this stage of working with your phone you won't see the F: drive pop up until we fully get you downgraded and get the ROM operational.
See what you can do with this link. Follow it and even redownload items from it. It's more updated then the one you used.
http://forum.xda-developers.com/showthread.php?t=928370
And let me know how it goes, and if I helped click the little thanks button~ like i said before I'll have time tonight to go back and forth and try and make this work. You just need to read your face off. HTC's can be tricky but at least it's not MOTOROLA...
---------- Post added at 05:11 PM ---------- Previous post was at 04:52 PM ----------
Found another thread too
http://forum.xda-developers.com/showthread.php?t=1538859&page=6
Page 4 has a link to some PD15IMG.zip files that could work, Page 5 has someone confirming which one works and then Page 6 this guy posts a video on how he fixed his.
Also make sure the phone is charged a low battery can cause boot loops, try and format the SD card and only have PD15IMG.zip be the only file.
lol I missed the fact that he's still in bootloader.
Bro just try flashing that stock img again
tonyMEGAphone said:
First in your Hboot screen scroll with the volume button to "Recovery" and let me know what happens.
---------- Post added at 04:36 PM ---------- Previous post was at 04:29 PM ----------
Also did you go to tmobile and install the HTC drivers under the support menu for your phone?
These are all must I read through your post and also am currently reading the link you said you followed but if you didn't do all these prerequisite work it's no wonder why you froze up.
---------- Post added at 04:52 PM ---------- Previous post was at 04:36 PM ----------
I see, you said the Recovery goes black and vibrates 7 times. Something didn't install right. At this stage of working with your phone you won't see the F: drive pop up until we fully get you downgraded and get the ROM operational.
See what you can do with this link. Follow it and even redownload items from it. It's more updated then the one you used.
http://forum.xda-developers.com/showthread.php?t=928370
And let me know how it goes, and if I helped click the little thanks button~ like i said before I'll have time tonight to go back and forth and try and make this work. You just need to read your face off. HTC's can be tricky but at least it's not MOTOROLA...
---------- Post added at 05:11 PM ---------- Previous post was at 04:52 PM ----------
Found another thread too
http://forum.xda-developers.com/showthread.php?t=1538859&page=6
Page 4 has a link to some PD15IMG.zip files that could work, Page 5 has someone confirming which one works and then Page 6 this guy posts a video on how he fixed his.
Also make sure the phone is charged a low battery can cause boot loops, try and format the SD card and only have PD15IMG.zip be the only file.
Click to expand...
Click to collapse
Ok Im going to try this now. Just hold on in there for me.
Lets see if this works
tonyMEGAphone said:
First in your Hboot screen scroll with the volume button to "Recovery" and let me know what happens.
---------- Post added at 04:36 PM ---------- Previous post was at 04:29 PM ----------
Also did you go to tmobile and install the HTC drivers under the support menu for your phone?
These are all must I read through your post and also am currently reading the link you said you followed but if you didn't do all these prerequisite work it's no wonder why you froze up.
---------- Post added at 04:52 PM ---------- Previous post was at 04:36 PM ----------
I see, you said the Recovery goes black and vibrates 7 times. Something didn't install right. At this stage of working with your phone you won't see the F: drive pop up until we fully get you downgraded and get the ROM operational.
See what you can do with this link. Follow it and even redownload items from it. It's more updated then the one you used.
http://forum.xda-developers.com/showthread.php?t=928370
And let me know how it goes, and if I helped click the little thanks button~ like i said before I'll have time tonight to go back and forth and try and make this work. You just need to read your face off. HTC's can be tricky but at least it's not MOTOROLA...
---------- Post added at 05:11 PM ---------- Previous post was at 04:52 PM ----------
Found another thread too
http://forum.xda-developers.com/showthread.php?t=1538859&page=6
Page 4 has a link to some PD15IMG.zip files that could work, Page 5 has someone confirming which one works and then Page 6 this guy posts a video on how he fixed his.
Also make sure the phone is charged a low battery can cause boot loops, try and format the SD card and only have PD15IMG.zip be the only file.
Click to expand...
Click to collapse
So I found a new img file and the same thing happens. It says it's updating but doesnt make any progess and it looks like its frozen. What should I do?
N_otori0us_ said:
lol I missed the fact that he's still in bootloader.
Bro just try flashing that stock img again
Click to expand...
Click to collapse
tonyMEGAphone said:
First in your Hboot screen scroll with the volume button to "Recovery" and let me know what happens.
---------- Post added at 04:36 PM ---------- Previous post was at 04:29 PM ----------
Also did you go to tmobile and install the HTC drivers under the support menu for your phone?
These are all must I read through your post and also am currently reading the link you said you followed but if you didn't do all these prerequisite work it's no wonder why you froze up.
---------- Post added at 04:52 PM ---------- Previous post was at 04:36 PM ----------
I see, you said the Recovery goes black and vibrates 7 times. Something didn't install right. At this stage of working with your phone you won't see the F: drive pop up until we fully get you downgraded and get the ROM operational.
See what you can do with this link. Follow it and even redownload items from it. It's more updated then the one you used.
http://forum.xda-developers.com/showthread.php?t=928370
And let me know how it goes, and if I helped click the little thanks button~ like i said before I'll have time tonight to go back and forth and try and make this work. You just need to read your face off. HTC's can be tricky but at least it's not MOTOROLA...
---------- Post added at 05:11 PM ---------- Previous post was at 04:52 PM ----------
Found another thread too
http://forum.xda-developers.com/showthread.php?t=1538859&page=6
Page 4 has a link to some PD15IMG.zip files that could work, Page 5 has someone confirming which one works and then Page 6 this guy posts a video on how he fixed his.
Also make sure the phone is charged a low battery can cause boot loops, try and format the SD card and only have PD15IMG.zip be the only file.
Click to expand...
Click to collapse
When I went to recovery mode..it went to a black screen with like a green symbol and box. Then the entire screen went blank and I noticed the phone vibrated "7" times. What should I do?
Bolt34 said:
When I went to recovery mode..it went to a black screen with like a green symbol and box. Then the entire screen went blank and I noticed the phone vibrated "7" times. What should I do?
Click to expand...
Click to collapse
7 vibrates of death.
Dun dun daaaaaa.
That's a brick. I think.
Sent from my HTC Glacier
N_otori0us_ said:
7 vibrates of death.
Dun dun daaaaaa.
That's a brick. I think.
Sent from my HTC Glacier
Click to expand...
Click to collapse
So in other words...I can't fix the phone then?
N_otori0us_ said:
7 vibrates of death.
Dun dun daaaaaa.
That's a brick. I think.
Sent from my HTC Glacier
Click to expand...
Click to collapse
Couldn't that just be due to a low battery also?
---------- Post added at 05:08 PM ---------- Previous post was at 05:00 PM ----------
These people couldn't even get into the Bootloader. That's why I believe there is slightly still hope for you.
http://forum.xda-developers.com/showthread.php?t=2188591
tonyMEGAphone said:
Couldn't that just be due to a low battery also?
---------- Post added at 05:08 PM ---------- Previous post was at 05:00 PM ----------
These people couldn't even get into the Bootloader. That's why I believe there is slightly still hope for you.
http://forum.xda-developers.com/showthread.php?t=2188591
Click to expand...
Click to collapse
I made sure the phone was fully charged and I had it plugged in. That couldn't be it.
last
Bolt34 said:
I made sure the phone was fully charged and I had it plugged in. That couldn't be it.
Click to expand...
Click to collapse
My last thread attempt, and if this doesn't work. I'd say check out Craigslist for a new phone. My Glacier 4G antenna, the actual hardware, I believe is shot. So I'm going to have to down grade and run through a similar process so I can send it back for a replacement. These things can get tricky so I feel your bricked pain. I've bricked a Motorola Atrix before.
http://forum.xda-developers.com/showthread.php?t=2329869
If none of this works. It's time to put it in a shoe box and bury it in the back yard.
Good morning All!
This is my first post here, hopefully I post in the right place. I have an old TPT, perfect device for my kids, all it need to do is run Zoodles. Was running fine with CM9, then one day, a couple of months back, it got stock on the Lenovo boot splash. Was getting ready to move so it made it in a box.
Trying to fix it now. Nut looks like I am in need of some advice and direction.
This is what I have done so far.
Boot into recovery kernel and tried to restore from my backup I had done before putting CM9 on it. Tried factory reset, None of which works.
The closest I got is with the restore of my backup, then when It rebooted, Ut got past the first Lenovo boot splash, we see Nvidia splash, then Animated Lenovo splash start, then device turns off and then back on.
Within the recovery kernel when I look at the logs, there is complaints about /data being in read-only mode during restore. I cannot unmount or format /data.
I think at this stage my best chance is to restore to stock with NVFlash. I am a little uncomfortable doing this without some advice first as I have no clue where to start
Model number is: 1839-22f
Could anyone assist? I am a professional IT, but My android knowledge is limited.
Thank you.
Hi esimard.
Sadly it is not much I can help.
From what I read about the issues of this tablet, and since Lenovo didn't release a plain recovery method in case of software corruption (like a vanilla Android with an installer), the only way I understand it can be fixed is booting it in APX mode and try to fix it with nvflash commands.
You need to be sure that your APX mode is not locked. If it is locked, I don't know any solution since Lenovo don't want to release the bootloader keys for this tablet (because the tablet contains DRM software).
If you can execute nvflash command and you didn't get an error (disconnection), maybe you can recover it. But you need to have the images of the partitions and sadly I don't have those. And I had never tried the nvflash commands.
Sorry for not being helpful, but maybe someone else can give you better hints here.
I tried to document everything about this tablet here: http://forum.xda-developers.com/wiki/Lenovo_ThinkPad%20Tablet
I'm really willing to write on the wiki a tutorial on how to recover this tablet using nvflash.
Regards
---------- Post added at 09:31 PM ---------- Previous post was at 09:18 PM ----------
Why don't you try first the basic nvflash.exe commands to see if you have access to the APX Mode.
http://forum.xda-developers.com/showthread.php?t=1745450
Regards
Hey all! My Nexus 6P that has been on N Preview since day 2 is now stuck in a boot loop. It will usually just display the Google logo and then reboot. Sometimes it will get to the very beginning of the Android boot animation, but rarely.
Unfortunately, I didn't even know about the OEM Unucking setting until I've been trying to get my phone to boot again. I've tried using clearing cache, factory restore, adb sideload, and the flashing instructions Google provides. I've also tried using SkipSoft Android ToolKit with no avail as well. At this point I don't care if I end up with Marshmallow or back on N. I just want my phone working again xP
Does anyone have any ideas on how to restore my phone back to a working state? Thanks!
It also might be good to mention is I'm not all that well versed in a lot of the android development tools. I'm not afraid to get my hands dirty though.
UPDATE (Thanks @NeoAcheron)
While this didn't work for me, this seems to work for some.
NeoAcheron shared the OTA update Google sends out to go from N to Marshmallow. YMMV, so best of luck to you!
If anyone has any other idea's to try, I'd be eternally grateful!
And remember kids, always enable OEM Unlocking like good boys and girls. (Settings -> Developer Options -> OEM Unlocking)
JPT62089 said:
Hey all! My Nexus 6P that has been on N Preview since day 2 is now stuck in a boot loop. It will usually just display the Google logo and then reboot. Sometimes it will get to the very beginning of the Android boot animation, but rarely.
Unfortunately, I didn't even know about the OEM Unucking setting until I've been trying to get my phone to boot again. I've tried using clearing cache, factory restore, adb sideload, and the flashing instructions Google provides. I've also tried using SkipSoft Android ToolKit with no avail as well. At this point I don't care if I end up with Marshmallow or back on N. I just want my phone working again xP
Does anyone have any ideas on how to restore my phone back to a working state? Thanks!
It also might be good to mention is I'm not all that well versed in a lot of the android development tools. I'm not afraid to get my hands dirty though.
Click to expand...
Click to collapse
If you can use fastboot fastboot system that should work out wipe userdata
jaythenut said:
If you can use fastboot fastboot system that should work out wipe userdata
Click to expand...
Click to collapse
Unfortunately, that didn't seem to work
Code:
> fastboot format userdata
Creating filesystem with parameters:
Size: 58688266240
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14328190
Block groups: 438
Reserved block group size: 1024
Created filesystem with 11/3588096 inodes and 271280/14328190 blocks
target reported max download size of 494927872 bytes
erasing 'userdata'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.013s
From the bootloader page on the phone...
Code:
Console: NULL
Battery OK
Device is LOCKED
Qfuse Status: ENABLED
Off-mode-charge: ENABLED
Download Mode: DISABLED.
Also worth a note...
Code:
> fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.005s
format from stock recovery ?
@JPT62089 You are not alone. My Nexus 6P is experiencing the same problem now. Signed up for the Dev Preview, phone behaved strangely today, reboot the device as per usual, and now its stuck on the boot screen...
I have tried applying the preview OTA update, and the Factory firmware reset, with the same results as you.
This is awesome considering I didn't unlock the bootloader, because I would have thought installing stock firmware would be possible.
This sucks... Lets hope Google releases a fix soon.
---------- Post added at 03:02 PM ---------- Previous post was at 03:01 PM ----------
csjneek said:
format from stock recovery ?
Click to expand...
Click to collapse
Unfortunately telling the device to reset to factory doesn't help either. Seems like the latest update broke the OS completely.
Wooohooo! Glad I'm not the only one It's unfortunate to have such a major issue as Preview 3 has been extremely stable for me up until yesterday...
NeoAcheron said:
@JPT62089 You are not alone. My Nexus 6P is experiencing the same problem now. Signed up for the Dev Preview, phone behaved strangely today, reboot the device as per usual, and now its stuck on the boot screen...
I have tried applying the preview OTA update, and the Factory firmware reset, with the same results as you.
This is awesome considering I didn't unlock the bootloader, because I would have thought installing stock firmware would be possible.
This sucks... Lets hope Google releases a fix soon.
---------- Post added at 03:02 PM ---------- Previous post was at 03:01 PM ----------
Unfortunately telling the device to reset to factory doesn't help either. Seems like the latest update broke the OS completely.
Click to expand...
Click to collapse
JPT62089 said:
Wooohooo! Glad I'm not the only one It's unfortunate to have such a major issue as Preview 3 has been extremely stable for me up until yesterday...
Click to expand...
Click to collapse
The Developer Preview was never meant to be signed up by any average user without prior knowledge on Android Development. If you sign up for the beta program, then it's always imperative that you have the bootloader previously unlocked, in case this exact situation happen. Did you actually think that you can just sign up for the Beta program and hope that it will not cause any problems?
ttminh1997 said:
The Developer Preview was never meant to be signed up by any average user without prior knowledge on Android Development. If you sign up for the beta program, then it's always imperative that you have the bootloader previously unlocked, in case this exact situation happen. Did you actually think that you can just sign up for the Beta program and hope that it will not cause any problems?
Click to expand...
Click to collapse
I am a software technical lead, knowing full well what the implications might be of running beta software on any piece of computing equipment. However, not at any point when I signed up was there a statement that I need to unlock the bootloader. Booloader unlocking in my mind (and on previous devices, like the HTC One) was only required when you wanted to deviate from the Stock firmware on the device. This is stock firmware, from Google.
I'm generally quite excited to test new things and I report my findings often with details about my experience and how the software behaved upto that point. But this has left a bad experience and I am not participating in the program anymore due to this.
Coming back now to say "oh you shoulda known" is not constructive. I am interested in a solution, because Google pretty much bricked my device without me touching it. The update (and the beta version since the announcement) applied seamlessly, and was working fine until I rebooted the device today.
---------- Post added at 04:18 PM ---------- Previous post was at 04:09 PM ----------
Found this: https://www.reddit.com/r/Nexus6P/comments/4jzp1o/soft_bricked_nexus_6p_with_locked_bootloader_need/
Might be possible to reproduce the special ZIP file to create a "special" downgrade OTA zip file to unbrick it, just to unlock the bootloader (at the very least).
I will have to look into it later, as I am still at work, and need to tend to some other tasks before getting back to this.
Will keep everyone updated...
NeoAcheron said:
I am a software technical lead, knowing full well what the implications might be of running beta software on any piece of computing equipment. However, not at any point when I signed up was there a statement that I need to unlock the bootloader. Booloader unlocking in my mind (and on previous devices, like the HTC One) was only required when you wanted to deviate from the Stock firmware on the device. This is stock firmware, from Google.
I'm generally quite excited to test new things and I report my findings often with details about my experience and how the software behaved upto that point. But this has left a bad experience and I am not participating in the program anymore due to this.
Coming back now to say "oh you shoulda known" is not constructive. I am interested in a solution, because Google pretty much bricked my device without me touching it. The update (and the beta version since the announcement) applied seamlessly, and was working fine until I rebooted the device today.
Click to expand...
Click to collapse
Bootloader unlocks are extremely important if you want to do any system-level mods (rooting, flashing custom recoveries, rom). Not only does it allow you to deviate from stock firmwares, like you said, but it also opens a gateway in which you can just flash a factory image and resolve any potential problems that may arise from otherwise stock Android or any custom roms you have. And stock firmwares, whether from Google, Samsung or even Apple, don't always mean good, or even stable. They may be stable 99% of the time, but eventually bugs and glitches are bound to happen; that's why they are continually updated, and that's why the 2011 Samsung ICS brick fiasco happened.
I did not mean to insult you or anything in the reply. That being said, yes, you really should have known before venturing into flashing firmwares without unlocking the bootloader and creating a backup first. As for solution, have you recently installed any apps that may not be compatible with N? Can you boot into safemode and disable some apps? If you can actually go into safemode, check allow oem unlock, unlock the bootloader and reflash factory image.
ttminh1997 said:
Bootloader unlocks are extremely important if you want to do any system-level mods (rooting, flashing custom recoveries, rom). Not only does it allow you to deviate from stock firmwares, like you said, but it also opens a gateway in which you can just flash a factory image and resolve any potential problems that may arise from otherwise stock Android or any custom roms you have. And stock firmwares, whether from Google, Samsung or even Apple, don't always mean good, or even stable. They may be stable 99% of the time, but eventually bugs and glitches are bound to happen; that's why they are continually updated, and that's why the 2011 Samsung ICS brick fiasco happened.
I did not mean to insult you or anything in the reply. That being said, yes, you really should have known before venturing into flashing firmwares without unlocking the bootloader and creating a backup first. As for solution, have you recently installed any apps that may not be compatible with N? Can you boot into safemode and disable some apps? If you can actually go into safemode, check allow oem unlock, unlock the bootloader and reflash factory image.
Click to expand...
Click to collapse
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
NeoAcheron said:
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Glad you could make your phone work again. Make sure that you unlock your bootloader before unlocking or testing any new roms.
NeoAcheron said:
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Did you just flash every .img file? There does not appear to be any other way.
NeoAcheron said:
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Thanks for posting this NeoAcheron, I sideloaded this yesterday and was actually able to perform an adb sideload this time (found a handy tip... Once the phone is waiting for adb commands, unplug and plug it back into the computer as it may not already see it)
It didn't seem to immediately help, unfortunately. I let it bootloop for a while before giving up and then tried again last night. I had left it on my desk bootlooping for a while and then all of a sudden it was booted and waiting for me to set it up. I quickly did so and immediate went to settings to enable the OEM Flashing setting and just as I did so it went to the red warning screen and then proceeded to bootloop again... I tried to run fastboot flashing unlock again in hopes that my changing the setting took before it bootlooped, but still got the FAILED message. I've since tried every which way of factory resetting, sideloading again, leaving it for hours in bootloop, and still nothing
Anyone have any more ideas?
Maybe a dumb question...but
ttminh1997 said:
Glad you could make your phone work again. Make sure that you unlock your bootloader before unlocking or testing any new roms.
Click to expand...
Click to collapse
Deleted
---------- Post added at 10:19 PM ---------- Previous post was at 09:59 PM ----------
So you need to get this file: https://android.googleapis.com/packa...cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Can I flash this ( https://android.googleapis.com/packa...cd4f52b800.zip) in TWRP ? I am running N5...I wanted to go back to Marshmallow to be able to flash some roms.
Thanks
NeoAcheron said:
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file:
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Hey NeoAcheron. I'm having a similar issue. After years of flashing custom ROMs, I joined the Beta programme so I could do things 'properly' on my Nexus 6P. Been working fine for a fortnight, until today when it randomly froze, crashed, and is now stuck in a bootloop on the 'Google' screen. I can get into the bootloader menu, but every option I select takes me back to the 'Google' bootloop screen. I can't even get my PC to recognise it as a device so I can't sideload a workaround.
Any ideas, or is it basically useless? Google have offered me a replacement phone, but I'd like to try and rescue this one first
Thanks in advance
kristianj79 said:
Hey NeoAcheron. I'm having a similar issue. After years of flashing custom ROMs, I joined the Beta programme so I could do things 'properly' on my Nexus 6P. Been working fine for a fortnight, until today when it randomly froze, crashed, and is now stuck in a bootloop on the 'Google' screen. I can get into the bootloader menu, but every option I select takes me back to the 'Google' bootloop screen. I can't even get my PC to recognise it as a device so I can't sideload a workaround.
Any ideas, or is it basically useless? Google have offered me a replacement phone, but I'd like to try and rescue this one first
Thanks in advance
Click to expand...
Click to collapse
The first thing you could try wiping cache from the stock recovery, and see if it works. Do you have any data on the device that you desperately wanna save, and can't loose?
DJBhardwaj said:
The first thing you could try wiping cache from the stock recovery, and see if it works. Do you have any data on the device that you desperately wanna save, and can't loose?
Click to expand...
Click to collapse
Thanks DJBhardwaj - I'm all backed up. I just wanted to see if I could fix it myself because I'd rather not be without a decent phone for a week. I'm no expert and I usually need my hand holding, but I've managed to get out of a few scrapes in the past with custom ROMs and bootloops!
My issue is that I can't even access stock recovery. I can get into the fastboot menu using the hardware keys but selecting any ption from there throws the device into a bootloop again. I also can't get my PC to see the device and wrestle beck control using adb commands, so I'm a bit stuck :/
kristianj79 said:
Thanks DJBhardwaj - I'm all backed up. I just wanted to see if I could fix it myself because I'd rather not be without a decent phone for a week. I'm no expert and I usually need my hand holding, but I've managed to get out of a few scrapes in the past with custom ROMs and bootloops!
My issue is that I can't even access stock recovery. I can get into the fastboot menu using the hardware keys but selecting any ption from there throws the device into a bootloop again. I also can't get my PC to see the device and wrestle beck control using adb commands, so I'm a bit stuck :/
Click to expand...
Click to collapse
Have you tried on any other Windows or Mac PC? If you can get it to detect, then the problem would be pretty easily solved. To confirm if your device is being recognized, type in the following command in CMD/Terminal:
Code:
fastboot devices
If anybody can put up a step-by-step guide, or a video that shows how to properly install it all, I'm sure myself, and much of the community would appreciate it.
Recently, my laptop that I had ADB, and every tool imaginable for Androids, and specifically the Galaxy Series, took a huge dump on me and I lost it all. I installed it so long ago, that embarrassingly I've forgotten how I did it all. If someone could post how they rooted their GS7 (non-edge variant), I would be very appreciative. And I'm sure much of the community would be too. I'm embarrassed to even have to ask as someone who used to formerly develop mods on phones. But it is what it is. It's been so long since I've set it all up, and I've had to do so much since that time that I've simply forgotten how I did it/how to do it. Any help would be GREATLY appreciated. Thank you ahead of time...
I've tried following the instructions in the sticky above. I ran the 930X ROOT.TAR in the special version of ODIN. And every ran OK. It said "Success" and then rebooted. All seemed well, then it froze on the AT&T Boot Logo. What can I do from here? I know from history that this is one of the points that people panic and claimed "brick" (though I've never seen a real brick from rooting). Any help would be greatly appreciated
There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk
twizt3d said:
There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk
Click to expand...
Click to collapse
thank you for that. I'll check it out. Hopefully it'll get me past this bootscreen issue
yup. Great instructions. All set rooted now. Now time to play with xposed and V4A and the like. Yay
OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks
thanirs said:
OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks
Click to expand...
Click to collapse
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
52brandon said:
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can
Click to expand...
Click to collapse
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
Click to expand...
Click to collapse
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.
thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.
Click to expand...
Click to collapse
so you got it all figured out and running great now right? No other issues right?
Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33
twizt3d said:
Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33
Click to expand...
Click to collapse
Can you please try restoring to af2?
Thanks for the ping. I think so. One thing I ran into which I don't know if its related to rooting. When I am in a phone conversation, audio on the other end goes in and out after a few minutes into the call. This happens with bluetooth or not. Still figuring out this issue.
52brandon said:
so you got it all figured out and running great now right? No other issues right?
Click to expand...
Click to collapse
Seeing battery drain. So went back to stock /unroot for now.
I was not trying to root my phone but reflash to an earlier version. I tried the Prince version of Odin and it did not work. The version that ended up working is in this thread
http://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930a-edge-variant-afp-stock-t3415344
http://click.xda-developers.com/api...ww.mediafire.com/download/2t...din_3.12.3.rar
If you can help me fix this i will donate you for your time
Somehow deleted messed up Persists and need a backup.
We are in a similar situation, my adb wasn't fully working, couldn't root on 10.5.4, msm and went back to stock, realized my adb wasn't fully working, I did the OTA to 10.5.5 and then I rooted, lost fingerprint read. Personally, I value root far more than fingerprint function, already started customizing the phone so can't be bothered to wipe the phone. I am pretty sure you would regain the fingerprint function if you go back to fully stock. If you can't be bothered to do it yourself, I think it's just a matter of time until a toolkit that does it for you is updated for the 8 pro.
t-mizzle said:
We are in a similar situation, my adb wasn't fully working, couldn't root on 10.5.4, msm and went back to stock, realized my adb wasn't fully working, I did the OTA to 10.5.5 and then I rooted, lost fingerprint read. Personally, I value root far more than fingerprint function, already started customizing the phone so can't be bothered to wipe the phone. I am pretty sure you would regain the fingerprint function if you go back to fully stock. If you can't be bothered to do it yourself, I think it's just a matter of time until a toolkit that does it for you is updated for the 8 pro.
Click to expand...
Click to collapse
ive done used MSM Brick Fix along with just about every other stock. Nothing has worked only reason i am so panicky over it is being used for a project that im working on and really need all features to work
Is this for Global or EU? Have a look in my thread if you need an EU persist. I ended up bricking mine trying to fix it.
This seems quite a wide spread issue, MSM doesn’t fix it either
If no one can provide you with a fix, I would use adb to flash the stock boot image. If you are wiped and fully stock again, did you go through the setup again, if so, did the enrollment fail there or did it fail when you manually went there? I just don't see why it would fail when the phone is in the stock "first bootup" mode.
It fails during first setup, during any setup. Even after a full flash with msm tool. I think the persist partion somehow gets messed up.
All I had done is flashed stock boot img was then reset.
Interesting. Did you at any point have a working fingerprint scanner? I did, until I rooted.
Guitarfreak26 said:
It fails during first setup, during any setup. Even after a full flash with msm tool. I think the persist partion somehow gets messed up.
All I had done is flashed stock boot img was then reset.
Click to expand...
Click to collapse
you forgot to convert the persist image before flashing thats what caused your brick most likely.
---------- Post added at 09:56 AM ---------- Previous post was at 09:54 AM ----------
Dewaynelives said:
If you can help me fix this i will donate you for your time
Somehow deleted messed up Persists and need a backup.
Click to expand...
Click to collapse
If you on EU then there is a persist image on the Root thread. But remember you need to convert it to a raw img from sparse image before flashing.
Google simgtoimg tool
Yeah I didn’t convert it I think that was the issue.
And yes my fingerprint sensor worked perfectly up until a factory reset then nothing. On the other thread, Zige advised that Oneplus Finland are aware of the issue and said a fix will roll out ?
Guitarfreak26 said:
Yeah I didn’t convert it I think that was the issue.
And yes my fingerprint sensor worked perfectly up until a factory reset then nothing. On the other thread, Zige advised that Oneplus Finland are aware of the issue and said a fix will roll out ?
Click to expand...
Click to collapse
Ot..Oneplus Finland sound funny..Cause its a Chinese company and i am Finnish myself
Nekromantik said:
you forgot to convert the persist image before flashing thats what caused your brick most likely.
Click to expand...
Click to collapse
Is that something that should be common knowledge for users who are opting to root and have a tinker.
It's it easy enough to convert? It's there any way to save your device if this happens?
I know @guitarfreak has had a lot of issues and I think it's heading for RMA right Gfreak?
We need a thread about this.
dladz said:
Is that something that should be common knowledge for users who are opting to root and have a tinker.
It's it easy enough to convert? It's there any way to save your device if this happens?
I know @guitarfreak has had a lot of issues and I think it's heading for RMA right Gfreak?
We need a thread about this.
Click to expand...
Click to collapse
yes you just need the tool google simage2img
as long as you have a backup of the partition and can use the tool and have access to fastboot it can be saved as far as I know.
other user lost access to fastboot as he used MSMtool to revert back to stock so locked bootloader. If you want to flash the persist do not use msmtool
Nekromantik said:
yes you just need the tool google simage2img
as long as you have a backup of the partition and can use the tool and have access to fastboot it can be saved as far as I know.
other user lost access to fastboot as he used MSMtool to revert back to stock so locked bootloader. If you want to flash the persist do not use msmtool
Click to expand...
Click to collapse
Not that i have this happened to me but still. Witch is broken, msmtool or phones sofrware? I am using linux so msm would be pointless for me. Just out of coriousity and knoledge i am asking
dladz said:
Is that something that should be common knowledge for users who are opting to root and have a tinker.
It's it easy enough to convert? It's there any way to save your device if this happens?
I know @guitarfreak has had a lot of issues and I think it's heading for RMA right Gfreak?
We need a thread about this.
Click to expand...
Click to collapse
Yeah it’s in Poland now at the service centre. I asked for a refund for now as I’m not sure what’s happening with it. I hadn’t crossflashed anything prior to the sensor stopping. So I’m not sure what’s causing the fault.
---------- Post added at 01:24 PM ---------- Previous post was at 01:23 PM ----------
pyry666 said:
Not that i have this happened to me but still. Witch is broken, msmtool or phones sofrware? I am using linux so msm would be pointless for me. Just out of coriousity and knoledge i am asking
Click to expand...
Click to collapse
Previously with OP the MSMTOOL would fix anything. Even when moving over to AOSP ROMs. Now it seems the tool can not fix the partion. So when I flashed wrong partion then tried to fix again with the tool it locked the boot loader but wouldn’t boot into OS.
Guitarfreak26 said:
Yeah it’s in Poland now at the service centre. I asked for a refund for now as I’m not sure what’s happening with it. I hadn’t crossflashed anything prior to the sensor stopping. So I’m not sure what’s causing the fault.
---------- Post added at 01:24 PM ---------- Previous post was at 01:23 PM ----------
Previously with OP the MSMTOOL would fix anything. Even when moving over to AOSP ROMs. Now it seems the tool can not fix the partion. So when I flashed wrong partion then tried to fix again with the tool it locked the boot loader but wouldn’t boot into OS.
Click to expand...
Click to collapse
I know that. I am interested is it msmtool failure or something in os
From my understanding from looking across the forums the persist partion hasn’t been touched by MSM for a while. Which would mean it’s an OS fault.
Does the boot img even touch the persist partion as that’s the only thing that had been touched prior to the fault? I don’t have enough understanding on persist as I’d never seen the issue before lol
pyry666 said:
I know that. I am interested is it msmtool failure or something in os
Click to expand...
Click to collapse
this has nothing to do with msmtool.
msmtool was used by people to try and fix the fingerprint issue.
This only should happen if you flash wrong version boot img. If you do that then you will loose fingerprint.
Some people have lost fingerprint even if they said they used correct boot img.
only way to bring fingerprint back is to flash persist img back onto phone. but you need to use simg2img tool which converts the posted img from sparse to raw. you can only flash raw images.
when you extract the img from phone its in sparse format and not raw
Nekromantik said:
this has nothing to do with msmtool.
msmtool was used by people to try and fix the fingerprint issue.
This only should happen if you flash wrong version boot img. If you do that then you will loose fingerprint.
Some people have lost fingerprint even if they said they used correct boot img.
only way to bring fingerprint back is to flash persist img back onto phone. but you need to use simg2img tool which converts the posted img from sparse to raw. you can only flash raw images.
when you extract the img from phone its in sparse format and not raw
Click to expand...
Click to collapse
Im on Int version is there any way for me to fix it? i dont know anyone with the device myself so i have no way to get the file
Nekromantik said:
you forgot to convert the persist image before flashing thats what caused your brick most likely.
---------- Post added at 09:56 AM ---------- Previous post was at 09:54 AM ----------
If you on EU then there is a persist image on the Root thread. But remember you need to convert it to a raw img from sparse image before flashing.
Google simgtoimg tool
Click to expand...
Click to collapse
im on int myself . whats messed u is i have not flashed any files from other regions to cause this so i guess it has to do with root?
Dewaynelives said:
im on int myself . whats messed u is i have not flashed any files from other regions to cause this so i guess it has to do with root?
Click to expand...
Click to collapse
Well, in my case it has been caused by a factory reset. Yes, I was rooted before that, but everything worked fine - so maybe rooting was the cause and it became evident after the reset.
Oh, and I was only on EU ROM - so no cross-country flashing.
I'll wait for Oneplus fixing this, for me there is too little understanding what happens when flashing persist from a different phone.