Here was a Guide. Someone said people don't care about Me or My Work so...​
I followed the steps, but I can't get into bootloader mode. please help. When I reboot to bootloader, the screen is blank and doesn't respond to fast boot commands.
Noob here Never posted but I've lurked quite alot.
Installing magisk works fine, but not any GSI
I'm just getting bootloops, reboots every few seconds or stuck at the splash screen.
Restoring with EMMA works, so It's not bricked.
I've been struggling with this for over two days and I can't understand what's going wrong
RP1408 said:
I followed the steps, but I can't get into bootloader mode. please help. When I reboot to bootloader, the screen is blank and doesn't respond to fast boot commands.
Click to expand...
Click to collapse
Is Your LED Blue if you attech to USB? If yes, are your drivers not correctly installed...
strandplask said:
Noob here Never posted but I've lurked quite alot.
Installing magisk works fine, but not any GSI
I'm just getting bootloops, reboots every few seconds or stuck at the splash screen.
Restoring with EMMA works, so It's not bricked.
I've been struggling with this for over two days and I can't understand what's going wrong
Click to expand...
Click to collapse
Well, you can try:
fastboot flash super GSI.img (in fastbootd)
That may work... Let me know!
Hi.
I'm having problems unlocking my bootloader and accessing fastboot. I even installed Ubuntu because I thought the problem was my Windows drivers. No luck. It recognizes fastbootd thingie (adb reboot fastboot) and ADB commands, but button up and usb plug-in doesn't work, no matter the platform. Device info says it's unlockable, model is XQ-CT54, software version is 64.1.A.0.857. what I'm supposed to do? I can give more info if needed. Haven't tried flashing stock yet.
edit. Never mind, I got it, and on Windows! I just have to pick manually those Sony drivers from the list and feed them for device manager every time I use fastboot. Acceptable.
Ok I know this thread is for the 1 IV, but since this is basically a copy-paste of the previous tutorials for 1 III etc.: Is this procedure android 13 approved, for the IV series as well as for the III series? I myself have the 5 III but just recently a colleague asked me if there's a way to root their 5 IV which is why I stumbled over this thread in the first place.
Both of the phones are running on Android 13 since the end of December.
Retenor said:
Ok I know this thread is for the 1 IV, but since this is basically a copy-paste of the previous tutorials for 1 III etc.: Is this procedure android 13 approved, for the IV series as well as for the III series? I myself have the 5 III but just recently a colleague asked me if there's a way to root their 5 IV which is why I stumbled over this thread in the first place.
Both of the phones are running on Android 13 since the end of December.
Click to expand...
Click to collapse
If they have international version yes they can if they have US version no they can't
raven213 said:
If they have international version yes they can if they have US version no they can't
Click to expand...
Click to collapse
And this goes for III series as well as with Android 13 for either of the two? Once again sorry for asking this here but neither of us can afford a brick and I wouldn't get an answer in the 5 III thread anymore after someone seemed to have had issues there with A13
I
Retenor said:
And this goes for III series as well as with Android 13 for either of the two? Once again sorry for asking this here but neither of us can afford a brick and I wouldn't get an answer in the 5 III thread anymore after someone seemed to have had issues there with A13
Click to expand...
Click to collapse
I think with the III you should be able to root I know they just started blocking bootloader on the IV
raven213 said:
I
I think with the III you should be able to root I know they just started blocking bootloader on the IV
Click to expand...
Click to collapse
Both of us are located in europe so I'm guessing the bootloader block doesn't affect us in this case, guess I'll just have to try as soon as I find the time to do it
Has anyone tried flashing GSIs? I need help flashing lineage OS. After rebooting from fastboot I'm stuck at boot animation (waited ~20 minutes). AOSP GSI from android website works and boots in seconds but not lineage os, please help.
Miustone said:
You will be fine with it somehow!
All the Best for the future,
Miu
Click to expand...
Click to collapse
Duudddeee... Nooo...!
MOD EDIT: civil words
K. You know google caches pretty much the entire internet though right?
ParkourPaul said:
K. You know google caches pretty much the entire internet though right?
Click to expand...
Click to collapse
Most people will never do that and just jump off here. The point was to revert my contributions on the Xperia Forums and to take My Work aside from the Guides offline. There are still forks around and there might be cached copies of my Threads. But my personal support ends here and I won't continue my work for Xperias starting today. Please respect that and have a great time with your Device anyways!
Thread has been closed as OP @Miustone removed the content of the opening post.
Regards
Oswald Boelcke
Senior Moderator
Related
Dear All,
Before I start, please forgive the repetition, as I know this issue comes up a lot but I've searched all over and can't find a solution for my circumstance. If there's a post I've missed, please direct me there...:fingers-crossed:
I recently received a Lumia 800 with a Qualcomm bootloader, sim-locked to a UK network. The first thing I did was use NSSPro to remove the simlock, which was successful, but I also wanted to debrand and try a custom ROM..
I read round the issue a fair bit and was going to go down the Linux 'dd' route when I spotted the Windows flashing utilties. Ever keen for an easy life, I went ahead and flashed my handset with FunkyRom, apparently making two fatal errors; not backing up my partitions in Linux and not using Linux to do the flash. Laziness stopped me backing up and I'm aware I deserve what I get for that, but the warnings about flashing in Windows were a little harder to spot and I only found those after the event.
ANYWAY....
Unsurpisingly it turns out, the Windows flash bricked the 'phone. I can get it into Qualcomm bootloader mode in Windows and Linux, I can read the partition map (attached), flash it in NSSPro, 'dd' it in Linux and flash it with the Windows tools, but it won't boot past the Nokia logo. After initial flashing the battery went haywire as well and wouldn't hold it's charge much beyond ten minutes. The battery is fine, I have swapped it out for a new one and it works fine in another 'phone, so I'm not sure what that was about. One other thing to note is I've never been able to hard reset it after flashing, the combination of button presses does nothing, no matter how long I hold them down, all that happens is the 'phone reboots if I release the power button.
I've tried many reflashes, replacing the third partition etc but I think I'm just laying s**t on top of s**t now and would appreciate some guidance. I don't think it's terminally bricked because I can still read/write from/to it in Linux, NSSPro etc, but I'm normally a Nokia N9 man, so this partition structure is unknown, I don't know what I'm looking for.
Any help much appreciated, with the note that I realise I ballsed up not making a backup, so you can skip telling me I'm a fool, I'm getting that enough from the missus..!
Sorry for the looong first post,
Squid
Not sure about fixing it as I have the 710, but Im pretty sure you could RMA to the place you bought it, and they would be too lazy to do full checks on what you did to it, send it back to Nokia and send you a replacement
I've bricked tablets and GPUs and phones and RMA'd, and not once have they ever questioned what I did
One phone I RMA'd I'd flashed a German ROM to and everything was stuck in German, UK company just walked me through factory resetting it on the phone, didn't work obviously, so they gave me a new one
Just an idea if you can't fix it yourself
Other options would be taking it to a local phone repair store who have tools to flash bricked phones, there have been a few here who didn't read the "DO NOT FORMAT" posts, and hit the format button bricking their phones, took it to a repair store who flashed it back to a working state for them
Good luck
Hi and thanks for the reply.
I'll be honest, I'm a Nokia N9 man myself, I was hoping to unlock this one as a spare's spare (it looks and feels familiar), so I'm unlikely to be taking it for repair if I can't get it going myself, but it's interesting to hear you've never been questioned about any DIY work you may have done, I've always thought they'd be hot on that...?
I am holding out for a technical hint or two on something I may have borked during the flash itself, and whether that might be recoverable, after all I can get to the bootloader, just whatever I flash on top (FunkyRom, Rainbow Mod etc) just don't load. Also, why doesn't hard reset work on this 'phone? I have questions but I've run out of brains for answers.
Are there generic full partition dumps available to dd in Linux that would be like a vanilla image? Are there specific partitions that may be the problem? If it gets to the Nokia logo but no further, how far in the booting process has it come?
Squid
Hi John,
Maybe you can try this: http://forum.xda-developers.com/showpost.php?p=47076870&postcount=2
Otherwise I can download an original rom for you, maybe you can flash that with nss, just let me/us know.
Greetz,
Rataplan said:
Hi John,
Maybe you can try this: http://forum.xda-developers.com/showpost.php?p=47076870&postcount=2
Otherwise I can download an original rom for you, maybe you can flash that with nss, just let me/us know.
Greetz,
Click to expand...
Click to collapse
Brilliant, I'll take a look at the NSU first, thanks!
Rataplan,
No joy with the NSU Retail I'm afraid. Do you think you could let me have an original ROM please as mentioned? After that, I guess it goes to the bin..
John
Ok, gonna download and upload this evening, keep you informed.
Greetz,
Rataplan said:
Ok, gonna download and upload this evening, keep you informed.
Greetz,
Click to expand...
Click to collapse
Great, thanks!
john smash said:
Great, thanks!
Click to expand...
Click to collapse
Ok John, you can download the rom here: https://dl.dropboxusercontent.com/u/9417919/rm-801.7z , the rom is based on RM801_059L8M3_1750.0805.8773.12220, I also suggest to read this: http://forum.xda-developers.com/showthread.php?t=1457341 and
this: http://forum.dailymobile.net/index.php?topic=77419.0
Greetz,
Many thanks, I'll try it later. I have actually tried those threads you linked previously but I'll take another look.
Cheers,
John
Hey there Rataplan,
No dice I'm afraid. I can't get the phone connected in anything other than Qualcomm mode, so I can't use NCS to flash. I can use NSSPro to flash a file with .nb extension but not the files you uploaded. NSU Retail asks me to connect in Qualcomm mode then doesn't recognise the phone once I do that.
I just don't understand how if I can get to the Qualcomm bootloader, why flashing RainbowMod or FunkyRom/FunkyRom lite doesn't work, do you have any suggestions? Is there a way to check if any of my partitions are corrupted?
JS
EDIT - Just read this post - http://forum.xda-developers.com/showpost.php?p=29583840&postcount=2 and renamed the boot.img of the ROM you uploaded. Now my 'phone shows a 'Three UK' splash screen, then the nokia logo, but still doesn't load. Is there a way to know what stage of the boot the 'phone is getting to before it hangs?
Ha! Got it!
Using the extract and rename method I flashed the 11412 firmware (oldest one in Navifirm) for product code 059M062 and bingo! It boots and there's no simlock...
Thanks for all your help Rataplan, 'phone revived!
:victory:
Great, I know it had to work, that's why I gave you an copy of an older rom, I'm glad you solved it yourself , take care next time.
Greetz,
Rataplan said:
Great, I know it had to work, that's why I gave you an copy of an older rom, I'm glad you solved it yourself , take care next time.
Greetz,
Click to expand...
Click to collapse
Will do..
I've changed my product code with NSSPro but if I try to flash any later ROMS then it goes back to being borked. I can always recover to this ROM now but I'm wondering why I can't upgrade?
john smash said:
Will do..
I've changed my product code with NSSPro but if I try to flash any later ROMS then it goes back to being borked. I can always recover to this ROM now but I'm wondering why I can't upgrade?
Click to expand...
Click to collapse
I have to take a look at your product code, did you try Nokia Update Retrailer.
The original product code was 059L7C6, I've successfully flashed it with a ROM for product code 059M062 and confusingly, I've written the product code 059L7C2 with NSSPro..
Does it bork it if you try to update it through Zune ?
*Detection* said:
Does it bork it if you try to update it through Zune ?
Click to expand...
Click to collapse
Hey,
Just plugged it into Zune now and it's offering me 7.10.7740.16. Question: Does using Zune overwrite the Qualcomm bootloader? Once that's gone I know I can't get any custom ROMS loaded on here..
Thanks,
JS
For those who may be interested:
I've got a working Lumia now, flashed with a 12220 firmware on a UK product code but that's it, I can't get anything more up to date on there. Every time I flash something more recent I get stuck at the Nokia screen. In addition, I get the same result with any of the custom ROMs, they just won't load. Could my hardware version be preventing the upgrade? Any ideas..?
JS
john smash said:
Hey,
Just plugged it into Zune now and it's offering me 7.10.7740.16. Question: Does using Zune overwrite the Qualcomm bootloader? Once that's gone I know I can't get any custom ROMS loaded on here..
Thanks,
JS
Click to expand...
Click to collapse
No the update doesn't overwrite the bootloader, I flashed the unlocked bootloader to mine and have flashed custom & stock & custom & stock in that order and everything stayed unlocked
OK so I might have screwed up my prime. I've done command line stuff and had custom ROMs on everything I own. But I am by no means an expert so please bear with me. I will explain my series of events to the best of my ability.
Starts off with a buggy ROM, i loaded it some time ago and have been dealing with it since. It was cm10 dated sometime in the middle of 2012. Did some searching and found that all the new ROMs were saying something about needing to nvflash to get blobs or something. No prob. Right?
Got everything prepared based off of these instructions:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Downloaded recovery_tf201.img, fastboot, nvflash, and the drivers. The very first step went ok. It showed moving the .img and then flashing the file. When done the little blue bar went across the screen like it should have.
Here's were it all went bad. I ran the reboot command in fastboot, device rebooted, loaded android. I held power a sec and chose "reboot recovery". I can now get the device to do one of three things:
1. Asus splash screen showing device unlocked when powered normally. That's it.
2. Hold vol down gets asus screen with 4 lines: this device is unlocked, android cardhu-user bootloader 2.10 e, checking for ota recovery, and booting recovery kernal image. Stops there.
3. Volume up gets black screen apx mode
Also tried running battery dead. Still same thing.
Is there any hope for my prime?
Where did I go wrong? Was it by pressing "reboot recovery" from the os?
Arggg please help. Otherwise a guide to replace the main board would be great.
Anything else please ask.
Thanks all,
Nick
Username5.2 said:
OK so I might have screwed up my prime. I've done command line stuff and had custom ROMs on everything I own. But I am by no means an expert so please bear with me. I will explain my series of events to the best of my ability.
Starts off with a buggy ROM, i loaded it some time ago and have been dealing with it since. It was cm10 dated sometime in the middle of 2012. Did some searching and found that all the new ROMs were saying something about needing to nvflash to get blobs or something. No prob. Right?
Got everything prepared based off of these instructions:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Downloaded recovery_tf201.img, fastboot, nvflash, and the drivers. The very first step went ok. It showed moving the .img and then flashing the file. When done the little blue bar went across the screen like it should have.
Here's were it all went bad. I ran the reboot command in fastboot, device rebooted, loaded android. I held power a sec and chose "reboot recovery". I can now get the device to do one of three things:
1. Asus splash screen showing device unlocked when powered normally. That's it.
2. Hold vol down gets asus screen with 4 lines: this device is unlocked, android cardhu-user bootloader 2.10 e, checking for ota recovery, and booting recovery kernal image. Stops there.
3. Volume up gets black screen apx mode
Also tried running battery dead. Still same thing.
Is there any hope for my prime?
Where did I go wrong? Was it by pressing "reboot recovery" from the os?
Arggg please help. Otherwise a guide to replace the main board would be great.
Anything else please ask.
Thanks all,
Nick
Click to expand...
Click to collapse
2. Hold vol down gets asus screen with 4 lines: this device is unlocked, android cardhu-user bootloader 2.10 e, checking for ota recovery, and booting recovery kernal image. Stops there.
Can you post a screen-shot of this ?
Thx Josh
See if this works.
Username5.2 said:
See if this works.
Click to expand...
Click to collapse
When on that screen does the PC see it as anything in device manager ?
So you do have your nvflash files backed up ?
Thx Josh
No it is not picked up by the PC at all.
And no I had just flashed the custom recovery with fastboot. Had not done anything else. Next step was to run wheelie. Didn't get that far.
Username5.2 said:
No it is not picked up by the PC at all.
And no I had just flashed the custom recovery with fastboot. Had not done anything else. Next step was to run wheelie. Didn't get that far.
Click to expand...
Click to collapse
Well, with no fastboot or adb an no nvflash a motherboard is the only way ...
Sorry for the crappy news ....
Thx Josh
lj50036 said:
Well, with no fastboot or adb an no nvflash a motherboard is the only way ...
Sorry for the crappy news ....
Thx Josh
Click to expand...
Click to collapse
Probably; but: screenshots show, that it is a tf101 (Eee Pad Transformer). I thought that I read in the forums some workaround, because it has no encrypted bootloader. Can be wrong, I'm no expert. Search!
edit:
Found it:
lilstevie said:
There is no concept of locked or unlocked in the tf101 bootloader, in the most general sense it is unlocked as it allows booting of unsigned kernels, and flashing of unsigned blobs.
the leaked key allows lower level communication (bootrom) with the device and can recover from bootloader errors.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22408864&postcount=3
Josh, thanks. And no problem on the crappy news. I kinda figured this was the case.
OK well after searching eBay and forums, I'm going to just get another prime. $80 for the logic board or $100 for a whole working tablet. So I will let this one sit awaiting a fix or a cheap logic board.
In the mean time can someone tell me where I screwed up?
I hate stock ROMs, and the sound of an "unbrickable tablet" by flashing new recovery is appealing. For that I will be attempting to back up these nvflash files on my new prime but I don't want another expensive paperweight.
So 2 questions.
Where did it all go wrong?
Am I following the set of instructions you all would recommend? I did get the link from this forum.
Thanks again.
das chaos said:
Probably; but: screenshots show, that it is a tf101 (Eee Pad Transformer). I thought that I read in the forums some workaround, because it has no encrypted bootloader. Can be wrong, I'm no expert. Search!
Click to expand...
Click to collapse
It is def. A tf201. All that writing in the screenshot is new except "the device is unlocked" since I flashed the recovery image from the link.
das chaos said:
Probably; but: screenshots show, that it is a tf101 (Eee Pad Transformer). I thought that I read in the forums some workaround, because it has no encrypted bootloader. Can be wrong, I'm no expert. Search!
edit:
Found it:
http://forum.xda-developers.com/showpost.php?p=22408864&postcount=3
Click to expand...
Click to collapse
Its a really old bootloader, that is the way they use to look....
Thx Josh
Username5.2 said:
Josh, thanks. And no problem on the crappy news. I kinda figured this was the case.
OK well after searching eBay and forums, I'm going to just get another prime. $80 for the logic board or $100 for a whole working tablet. So I will let this one sit awaiting a fix or a cheap logic board.
In the mean time can someone tell me where I screwed up?
I hate stock ROMs, and the sound of an "unbrickable tablet" by flashing new recovery is appealing. For that I will be attempting to back up these nvflash files on my new prime but I don't want another expensive paperweight.
So 2 questions.
Where did it all go wrong?
Am I following the set of instructions you all would recommend? I did get the link from this forum.
Thanks again.
Click to expand...
Click to collapse
The bootloader is to old to flash that recovery, that is where you went wrong ....
Thx Josh
Username5.2 said:
OK so I might have screwed up my prime. I've done command line stuff and had custom ROMs on everything I own. But I am by no means an expert so please bear with me. I will explain my series of events to the best of my ability.
Starts off with a buggy ROM, i loaded it some time ago and have been dealing with it since. It was cm10 dated sometime in the middle of 2012. Did some searching and found that all the new ROMs were saying something about needing to nvflash to get blobs or something. No prob. Right?
Got everything prepared based off of these instructions:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Downloaded recovery_tf201.img, fastboot, nvflash, and the drivers. The very first step went ok. It showed moving the .img and then flashing the file. When done the little blue bar went across the screen like it should have.
Here's were it all went bad. I ran the reboot command in fastboot, device rebooted, loaded android. I held power a sec and chose "reboot recovery". I can now get the device to do one of three things:
1. Asus splash screen showing device unlocked when powered normally. That's it.
2. Hold vol down gets asus screen with 4 lines: this device is unlocked, android cardhu-user bootloader 2.10 e, checking for ota recovery, and booting recovery kernal image. Stops there.
3. Volume up gets black screen apx mode
Also tried running battery dead. Still same thing.
Is there any hope for my prime?
Where did I go wrong? Was it by pressing "reboot recovery" from the os?
Arggg please help. Otherwise a guide to replace the main board would be great.
Anything else please ask.
Thanks all,
Nick
Click to expand...
Click to collapse
Username5.2 - We are sorry to hear about this issue you are having and we are more than happy to assist you. Please email us at [email protected] with your serial number and this post attached for assistance.
If you have any further questions, comments, or concerns please do not hesitate to let us know. We will be more than happy to assist you. Once again, thank you for choosing ASUS products and services.
Thank you,
-In Search of Incredible-
Technical Support Department
http://www.asus.com :: http://service.asus.com/
lj50036 said:
Its a really old bootloader, that is the way they use to look....
Thx Josh
The bootloader is to old to flash that recovery, that is where you went wrong ....
Thx Josh
Click to expand...
Click to collapse
Dang. I followed a link from this forum @
http://forum.xda-developers.com/showthread.php?t=1774352
That led me to this link I posted above:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
So that guide had me download an incorrect file? The files were downloaded right from that page. Check it out.
Username5.2 said:
Dang. I followed a link from this forum @
http://forum.xda-developers.com/showthread.php?t=1774352
That led me to this link I posted above:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
So that guide had me download an incorrect file? The files were downloaded right from that page. Check it out.
Click to expand...
Click to collapse
Your firmware version is 9.4.2.21 which is Android version 4.0.3 'ICE CREAM SANDWICH'
The guide is for 'JELLYBEAN' bootloaders....
That is why flashing said file was the wrong thing to do...
Sorry for the bad new... :crying:
Thx Josh
Okay so my phone randomly rebooted 2 days ago and when it got to the LG logo screen it froze. I tried to hard reset it, i went in to the hard reset menu clicked yes once then confirmed the hard reset by selecting yes a second time and the phone froze on highlighted yes. I have pulled the battery and tried to do this multiple times to no avail. So next i went to my PC and started google searches. Often i found things such as being stuck in boot loop which my phone wasn't, it was just frozen at the LG logo screen. Regardless I like to think of myself as self educated tech savvy (which now from reading all of your posts im not, im not even a little bit, in fact im tech stupid.) I did follow post through to the LGUP tool and downloaded a stock KDZ and got my phone into download mode>firmware update screen, i was able to get al the correct drivers and get LGUP to recognize the device and i loaded the stock KDZ and tried to do a Complete wipe reinstall. The program as able to interact with my device and went through the process, i thought i had fixed my phone. After a fresh install(or what i thought was a fresh install) i rebooted after the update and went to the LG logo screen and froze. The only difference is now when my phone starts, right before the LG logo appears i get the green android robot with what looks like open working "guts" real quick before it goes to the Logo and freezes. So back to the drawing board and i wanted to attempt some of the things ive seen like TWRP recovery etc but here i am getting lost. Forgive me if im posting things that have been answered but i keep getting confused. I dont know what the difference is between fastboot boot loader recovery mode or any of that is. also i kept noticing time and time again that my phone has to be in USB debugging mode and i dont know if it is. I cant turn my phone on to get it into USB debugging mode now anyways. Im okay with my warranty being voided and im okay with rooting if thats what i have to do to make it work. I have installed ADB and fastboot and some twrp recoveries etc but im clueless. Lastly know that i never Rooted my phone or anything but i was a torrent downloader. forgive me im triyng to provide as much information as possible.
PLEASE NOTE - I had to sign up to post here obviously and i loved how it said if you have an IOS go buy an android and come back LOL
Message Tung Kick. He can get u out of anything
Hit thnx if this helpd
tried
joshualuna said:
Message Tung Kick. He can get u out of anything
Hit thnx if this helpd
Click to expand...
Click to collapse
i tried to message tung kick and it said user not found?
sjeffreysmith said:
i tried to message tung kick and it said user not found?
Click to expand...
Click to collapse
Use Messenger on FB
i appreciate the resonse
joshualuna said:
Use Messenger on FB
Click to expand...
Click to collapse
is that the name to search for on fb? "tung kick"
sjeffreysmith said:
is that the name to search for on fb? "tung kick"
Click to expand...
Click to collapse
Try again on here but lower case and name is one whole wrd. tungkick
joshualuna said:
Try again on here but lower case and name is one whole wrd. tungkick
Click to expand...
Click to collapse
not having luck with him yet but ill keep trying. is there any other posts or something you could point me towards?
sjeffreysmith said:
not having luck with him yet but ill keep trying. is there any other posts or something you could point me towards?
Click to expand...
Click to collapse
http://forum.xda-developers.com/tmobile-lg-v10/development/debrick-phone-h901-qualcomm-9008-t3440359
This thread by him may help.
jsu718 said:
http://forum.xda-developers.com/tmobile-lg-v10/development/debrick-phone-h901-qualcomm-9008-t3440359
This thread by him may help.
Click to expand...
Click to collapse
SD card my only option?
Hello guys!
I need a big help!
I have a meizu pro 7 (128GB). Have a bootloop and want now flash again with the stockrom "Variation A".
I can start in fastboot variation.
Who can help me? I have downloaded the last flyme-rom.
What did i have to do to "unbrick" my phone?
Thanks for help!
Best regards peter
Hello guys!
I have solved the problem!
When you start the phone in "recovery mode" and connect the phone to a computer so you will find a drive with "recovery". At this drive you can copy an "update.zip" (a-rom) and start at the phone. So it will restart and reboot.
I hopy anyone can use it.
best regards
peter
Did you ever figure out if this is possible?
Im in a bootloop and the recovery on this phone only give 2 options ive been trying to figure out how to sideload but without a proper recovery i cant do iot
fastboot takes commands but without a bootloader unlock and a recovery worth a **** i think its a fools errand. meizu is no help ive heard either
If you have damaged the stock recovery image, there is no option to restore. you need to pack the phone and send it to a Meizu dealer for reflash.
I have a brand new pro 7 plus Stuck at the FLYME with the turning logo . Shame really I didn't do anything out of the ordinary and now it's a 600 paperweight. Where is a service e center ? Nightmare this is ......I even contacted Meizu directly they basically told me to go @#$% myself ...
herb9876 said:
I have a brand new pro 7 plus Stuck at the FLYME with the turning logo . Shame really I didn't do anything out of the ordinary and now it's a 600 paperweight. Where is a service e center ? Nightmare this is ......I even contacted Meizu directly they basically told me to go @#$% myself ...
Click to expand...
Click to collapse
If its on Logo rotating, the bootloader probably is fine. You need to find the same version of the software that you have had on your phone. Then you go to recovery and flash it. There are two ticks, before the flash process begins. Mark both. Flash, reboot and it should be as good as new.
I wish you were right but I've tried flashing every fw under the sun and it's either corrupt or too old. I'm all ears though if you have suggestions going forward . You are correct in describing my situation. Thanks in advance
herb9876 said:
I wish you were right but I've tried flashing every fw under the sun and it's either corrupt or too old. I'm all ears though if you have suggestions going forward . You are correct in describing my situation. Thanks in advance
Click to expand...
Click to collapse
Hi, I'm sorry dude but we're in the same boat. There is a problem with the Chinese variant, when you flash a beta A firmware and then flash the G firmware, the phone gets stuck and you can't update to any firmware anymore. We asked Meizu on the Flyme forums for a while (it's been a while our phone is useless), a moderator said not long ago that apparently they will release a new firmware which fixes that, I'm not certain about it but it's our best bet at this point. Either that, or if someone with enough knowledge manages to find a way to unlock the bootloader.
Here is the link to the bug report if you want to click the "I have the same" button and, maybe make them hurry a bit?
http://forum.flymeos.com/thread-38010-1-1.html
herb9876 said:
I wish you were right but I've tried flashing every fw under the sun and it's either corrupt or too old. I'm all ears though if you have suggestions going forward . You are correct in describing my situation. Thanks in advance
Click to expand...
Click to collapse
Have you searched this site ?
https://reameizu.com
how to enter in fastboot mode meizu pro 7 plus ?
Here is TWRP 3.2.1 build for Project Tango K1 ATAP.
Download
gdrive: twrp-3.2.1-yellowstone.img
mailru: twrp-3.2.1-yellowstone.img
Sources
device tree: https://github.com/HighwayStar/android_device_google_yellowstone
kernel: https://github.com/HighwayStar/android_kernel_google_yellowstone
How to install
enable USB debugging in stock ROM and run command: adb reboot bootloader
Unlock bootloader using command: fastboot oem unlock (it will wipe all your user data!)
With unlocked bootloader boot into stock rom and enable USB debugging again. Reboot to bootloader: adb reboot bootloader
Flash recovery image: fastboot flash recovery twrp-3.2.1-yellowstone.img
To boot into recovery you could run adb reboot recovery after booting to stock ROM or use Vol+ Vol- Power combo to boot in bootloader menu and select Recovery using volume keys and confirm by pressing Power.
XDA:DevDB Information
[RECOVERY][TWRP] Project Tango K1 ATAP TWRP 3.2.1, Tool/Utility for the Nvidia Shield Tablet
Contributors
highwaystar_ru
Source Code: https://github.com/HighwayStar/android_kernel_google_yellowstone
Version Information
Status: Testing
Created 2019-02-19
Last Updated 2019-02-19
Any ROMs available for yellowstone? I can see one in use on the LineageOS Statistics page (search 14.1-20190208-UNOFFICIAL-yellowstone)
But I can't find it on xda.
I didn't get it to boot, but I was in a hurry and hopefully just forgot something simple. If anyone gets it working please post details. Hopefully this is legit:
Edit: link removed. Per the developer: "please don't use them. They're experimental, and won't be booting for some time... you run the chance of bricking. Definitely stay away until I make some form of announcement otherwise."
@highwaystar_ru gave me this ROM that is working splendidly on my yellowstone: https://cloud.mail.ru/public/Hmco/XryszodXm
From @highwaystar_ru:
It uses binary files from stock yellowstone and has some issues:
cameras doesnt work, video playback sometimes has artifacts, all cpu
cores always up (without it video playback lags), accelerometer sensor
inverted.
Me and couple of lineage devs working hard to port shieldtablet kernel
to yellowstone, it will allow to use shield binary files and resolve
most problems, but progress are really slow (but there is some
progress lately).
Click to expand...
Click to collapse
shiznit1618 said:
@highwaystar_ru gave me this ROM that is working splendidly on my yellowstone: https://cloud.mail.ru/public/Hmco/XryszodXm
From @highwaystar_ru:
Click to expand...
Click to collapse
Thanks! This is working very well so far for the limited testing I've done. I'll have to take it into the field and see how that goes .
Tried out that ROM , it's pretty good outside of issues listed bluetooth is non functional.
Mobile data , text, wifi etc working.
Back to life
Thanks to highwaystar_ru I was able to install twrp and then lineage 14.1 with Open GApps pico.
I hope that somebody will be able to bring this to 15.1
Please keep up your effort, Hurray I can use my tango again , at least some of it, would be great that bluetooth and cameras working and good luck with the shield software i'll be looking for it . Thanks alot
thanks
worked for me. . with all the restrictions added.. but still brought a perfectly fine tablet from no usage to home automation dashboard device
Great work thank you,
Also i tested that Rom in the thread and it works well despite the reversed sensor, bluetooth (and i report USB on dock non fuctional with rom)
has there been any progress on the Rom at all? thanks.
Any progress with this rom?
Also @shiznit1618 and @highwaystar_ru where are you guys collaborating? If this is a telegram, discord, or other chat group. I'd love to get in and talk, maybe help a bit. I'm currently on arcore devs slack chat but there isn't much activity in their #yellowstone channel.
https://arcore.slack.com
ShapeShifter499 said:
Any progress with this rom?
Also @shiznit1618 and @highwaystar_ru where are you guys collaborating? If this is a telegram, discord, or other chat group. I'd love to get in and talk, maybe help a bit. I'm currently on arcore devs slack chat but there isn't much activity in their #yellowstone channel.
https://arcore.slack.com
Click to expand...
Click to collapse
There does seem to be some active development on GitHub (within the last week) and I also found (from same developer on GitHub) a newer rom based on 15.1 although I couldn't get it to boot, seems I need to update TWRP, but trying to update TWRP it tells me the recovery partition exceeded size, so I assume I have to update boot as well (which I didn't do). i'd suggest checking on GitHub and contacting that developer.
https://github.com/TegraDevelopment/android_device_google_yellowstone
Bazathoth said:
There does seem to be some active development on GitHub (within the last week) and I also found (from same developer on GitHub) a newer rom based on 15.1 although I couldn't get it to boot, seems I need to update TWRP, but trying to update TWRP it tells me the recovery partition exceeded size, so I assume I have to update boot as well (which I didn't do). i'd suggest checking on GitHub and contacting that developer.
https://github.com/TegraDevelopment/android_device_google_yellowstone
Click to expand...
Click to collapse
Where did you find the 15.1 build?
ShapeShifter499 said:
Where did you find the 15.1 build?
Click to expand...
Click to collapse
http://updater.ods.ninja/yellowstone
This is the same project I had mentioned in post #3. I took the link down because it wasnt ready at the time and I've been waiting for the dev to let us know when its working. See post #3 for a quote from him...
But... there is a build from Feb 12. Please let us know how it goes if you try it. :good:
xaxxelous said:
http://updater.ods.ninja/yellowstone
This is the same project I had mentioned in post #3. I took the link down because it wasnt ready at the time and I've been waiting for the dev to let us know when its working. See post #3 for a quote from him...
But... there is a build from Feb 12. Please let us know how it goes if you try it. :good:
Click to expand...
Click to collapse
I have a new issue, my tablet is rebooting constantly. It will crash to a "red battery icon" and then boot back up to the lockscreen. I'm not sure if the battery in my unit is bad or if the battery calibration is messed up. Do you have any ideas what to do here?
My device was restored to stock btw.
ShapeShifter499 said:
I have a new issue, my tablet is rebooting constantly. It will crash to a "red battery icon" and then boot back up to the lockscreen. I'm not sure if the battery in my unit is bad or if the battery calibration is messed up. Do you have any ideas what to do here?
My device was restored to stock btw.
Click to expand...
Click to collapse
Will it stay on while plugged into the dock? Or usb even?
xaxxelous said:
Will it stay on while plugged into the dock? Or usb even?
Click to expand...
Click to collapse
I never got a hold of a original dock, I didn't check to see if keeping it on charge helped.
ShapeShifter499 said:
I never got a hold of a original dock, I didn't check to see if keeping it on charge helped.
Click to expand...
Click to collapse
Did you flash that build from Feb 12?
How did you return to stock? A TWRP backup or do you have original firmware?
Does it keep bootlooping by itself without any input from you or will it sit stable at the lockscreen? Can you keep it turned off?
Depending on the answers to those questions, the first thing I would do is turn it off and plug it in. Let it sit until fully charged. It takes a long time via USB, and even longer if it is on. Not that this is a solution, just troubleshooting...
xaxxelous said:
Did you flash that build from Feb 12?
How did you return to stock? A TWRP backup or do you have original firmware?
Does it keep bootlooping by itself without any input from you or will it sit stable at the lockscreen? Can you keep it turned off?
Depending on the answers to those questions, the first thing I would do is turn it off and plug it in. Let it sit until fully charged. It takes a long time via USB, and even longer if it is on. Not that this is a solution, just troubleshooting...
Click to expand...
Click to collapse
It reboots without me touching. The main OS has a full battery icon but the reboot flashes the red battery icon before booting. I flashed using NVFlash a copy of the stock OS I got from the arcore stack. Someone gave me their APX package that NVFlash requires.
That file is here: https://drive.google.com/file/d/1dv5ZPsczOAp6l9WOgVlbCTuBnbW71L8p
Conversation starts here: https://arcore.slack.com/archives/C68HHETL7/p1549401595001100
Main quote of interest from that chat:
Greg Willard (r3pwn) 1:20 PM
Around 3 mins left on the upload
1:24
What I did in the interest of still letting a device turn on if someone didn't get the chance to back up their persist/persistbk, was I took mine, and scrubbed the mac addresses and serial number. So the macs are set to 00:11:22:33:44:55:66, and the serial num is 012345678.
1:25
... aaaand here you go https://drive.google.com/file/d/1dv5ZPsczOAp6l9WOgVlbCTuBnbW71L8p
Click to expand...
Click to collapse
ShapeShifter499 said:
It reboots without me touching. The main OS has a full battery icon but the reboot flashes the red battery icon before booting. I flashed using NVFlash a copy of the stock OS I got from the arcore stack. Someone gave me their APX package that NVFlash requires.
That file is here: https://drive.google.com/file/d/1dv5ZPsczOAp6l9WOgVlbCTuBnbW71L8p
Conversation starts here: https://arcore.slack.com/archives/C68HHETL7/p1549401595001100
Main quote of interest from that chat:
Click to expand...
Click to collapse
I can't see that convo without an account. Have you asked for help there?
Until I get home I can't really look at that apx. Maybe install TWRP and the ROM from post #4 or a TWRP backup? Without knowing what that apx flashed its hard to say. The ROM from highwaystar_ru (mostly) works. Might at least get you out of the bootloop.
And just to be clear, you did not flash that 15.1 build, right? What were you running before flashing the apx?
Unless TWRP and that LOS 14.1 ROM or a TWRP backup help we've gone off topic for this thread...