Hello. Sorry for my english. I want flash my phone via rootjoy to Arcatarc's MIUmIZERO and i only can see miui logo. next i want back to stock rom from needrom via sp flash tool, i followed instructions and i stop, when red status back not change for 20 minutes. and i can't charge my phone, can't conected to pc, can't turn on, looks like dead. How unbrick my phone? please help
problem solved
how did you solve it? please let me know as i am in the same boat
If it's stuck on the MIUI screen then it's possible the bootloader wasn't flashed properly.
If you can reboot the phone in fastboot you can flash the bootloader via PC.
it is dead . the phone wont turn on . the pc wont recognise it anymore , it was fine ... untill i tried to flash stock through sp flash tool .
i was running antarcts emui,.... tried flashing using the method on umi digi forum : http://umidigi.com/forums/topic/how-to-restore-rom-version-3-03-2/ ... preloader was unticked, and when i tried firmware uopgrade option...nothing happened, and the phone was dead after that.
thepopos said:
If it's stuck on the MIUI screen then it's possible the bootloader wasn't flashed properly.
If you can reboot the phone in fastboot you can flash the bootloader via PC.
Click to expand...
Click to collapse
I managed to make it boot.
The problem is I have twrp and some chinese recovery . And I cant go back to stock.
Fastboot cant flash recovery for some reason ... so I can go back to rootjoy.
use adb side load an try to flash a working rom, the original one from umi website or emui.
can you get in recovery mode? volume (+ or - try both) and power button for some seconds
if yes go adb side load, (check google) and transfer an original rom, then flash it again in the recovery
My Umi Zero is bricked, because I cannot mount /system. I can get into the TWRP, but I cannot do anything, even restore my backup because of this. Does anyone have idea what to do?
Pospa420 said:
My Umi Zero is bricked, because I cannot mount /system. I can get into the TWRP, but I cannot do anything, even restore my backup because of this. Does anyone have idea what to do?
Click to expand...
Click to collapse
If the system is unstable with popups etc or with damaged partitions you can get past that with TWRP.
Boot into recovery Wipe/Advanced Wipe. Then after that is completed, without rebooting, Format Data. That should sort out your partitions.
Then Install ROM from the recovery. It will need to be on the device. If your new ROM is not already there plug in a USB lead and transfer the zip file from your pc.
If you want to re-install your backup, do that instead.
If that doesn't work Backup in TWRP, even though there is no system. Then copy your Nandroid backup (must have been made via TWRP) and paste into the same folder as the Backup you just made, overwriting if asked.
I have had to do all this myself!
Good luck
Hi all!
I have the simular problem.
Umi Zero can not start.
But recovery seems to be working.
1) TWRP recovery 2.8.2
After full wipe, my TWRP recovery write "Unable to mount /SYSTEM"
The same message I have if I try to flash original 3.10 ROM via TWRP.
It is impossible to mount or format or repair SYSTEM via recovery
But it is possible to see files in FileManager and go to Fastboot and ADB mode
2) ADB and Fastboot mode.
Impossible to flash any partition.
"boot" - checksum error
"recovery" - "not support flash" message
"system" - filesystem created, start "erasing" and freeze. If I disconnect phone, have got message "failed (too many links)"
adb sideload does not work also
3) SP Flash Tool
I tried with full 3.10 ROM and with CRT 3.0 recovery
Download mode and Format+Download mode.
The same result: yellow bar finished and got message "Checksum error" or something like that.
All this experiments change nothing in phone. I still have TWRP recovery and "unable to mount /SYSTEM" message.
Any advices?
I am not English-speaking guy, as you guess), sorry.
It looks like memory become write-protected...
YrP said:
Hi all!
I have the simular problem.
Umi Zero can not start.
But recovery seems to be working.
1) TWRP recovery 2.8.2
After full wipe, my TWRP recovery write "Unable to mount /SYSTEM"
The same message I have if I try to flash original 3.10 ROM via TWRP.
It is impossible to mount or format or repair SYSTEM via recovery
But it is possible to see files in FileManager and go to Fastboot and ADB mode
2) ADB and Fastboot mode.
Impossible to flash any partition.
"boot" - checksum error
"recovery" - "not support flash" message
"system" - filesystem created, start "erasing" and freeze. If I disconnect phone, have got message "failed (too many links)"
adb sideload does not work also
3) SP Flash Tool
I tried with full 3.10 ROM and with CRT 3.0 recovery
Download mode and Format+Download mode.
The same result: yellow bar finished and got message "Checksum error" or something like that.
All this experiments change nothing in phone. I still have TWRP recovery and "unable to mount /SYSTEM" message.
Any advices?
I am not English-speaking guy, as you guess), sorry.
Click to expand...
Click to collapse
Hi
Did you Advance Wipe and Format Data?
I found that worked.
Alternatively, you could use Rootjoy to put just about any ROM on. CM 12.1 works ok.
Once you have a stable installation, install a custom recovery like TWRP 2.8.7 from Needrom. I used Mobileuncle, an app from the Playstore. However, I looked just now and it doesn't seem to be available.
I have tried Rashr, but couldn't get it to work.
Once you have it all stable you can flash the ROM you really want via TWRP.
Good luck
Advance Wipe and Format Data or flashing new stable ROM via TWRP did not work for me. The same result- unable to mount /system.
Rootjoy and Mobileuncle could be used if phone is working. My phone works in recovery mode only.
I tried to flash different recoveries but did not find the way to do this. As I wrote, Sp Flash Tool, Fastboot and Adb Sideload did not make any changes to my recovery. I think, flash new recovery will help if I found the way)
Or if I discover the method to test and\or repair /system partition from PC
But thank you for answer)
@YrP
Rootjoy works from your pc
Yes, Rootjoy- works)
But for establish connection phone must work too.
And not in recovery mode.
@YrP
I have already done all this with my daughter's Zero.
However, it's in bits at the moment while we wait for a part from China. So I can't go through the process with you live, step by step.
I am in the UK.
If you send the phone to me I will try and fix it for you.
PM me if you want to go ahead and I will let you have my address.
I am in Ukraine, it is too far from UK)
I will keep trying to find the way to fix it by myself.
But thank you very much for your attention and advices.
@YrP
I have got my daughter's phone back together and fixed (mostly).
Did you manage to get your Zero going?
Sent from my Nexus 4 using XDA-Developers mobile app
@goldbear
My UMI is still bricked(
It is flash memory problem, I think.
I am trying to find the tool to remap internal memory, to move SYSTEM part to other physical place. But did not find it yet.
What was your way?
Zero stutters, processes crash or the phone will not boot into System
Have you already tried a Factory Reset or re-installed the ROM?
What can you do?
You could try the following. However, if your phone blows up, orders a takeaway or elopes with your girl-friend, please don’t blame me.
1. Provided you already have TWRP custom recovery installed and your phone is powered down boot into Recovery: hold the volume down and power buttons until the Zero logo appears then let go
2. Select Wipe/Advanced and select Dalvik Cache, System, Cache and Data. Slide to execute
3. Select Format Data/ type yes and slide to execute
4. Reboot into Recovery without installing a new ROM
5. Select Backup, choose SD card rather than internal storage and give the file a memorable title like Blank Backup and date. Select Boot, Logo, Recovery and Uboot. Slide to execute
6. The next step requires you to have a Nandroid backup made via TWRP already made of a stable ROM. If it isn’t stable or you don’t have one I have attached a clean backup below. It’s derived from Cyanogen Mod 12.1. This is based on Lollipop 5.1, with Gapps and rooted. I have found this to work. As the title of the file suggests, it’s a factory reset, ie no personal data included. Download it to your pc unzip and save it.
7. Connect your phone to your pc via USB cable and open Windows Explorer
8. Find your stable backup or the one below and drill down until you see the folder with 15 files, starting with data.info and ending with uboot.emmc.win. Select all and Copy.
9. Open another window and find the TWRP folder on the SC card of your phone. Drill down to the same folder containing similar files as to step 8 above. Click in folder and Paste. When prompted select Copy and Replace, all and Ok
10. If your pc doesn’t show your phone and the SD card, in recovery select Mount and USB storage.
11. In Recovery select Restore and the Blank Backup (or whatever file name you gave it, now populated with usable ‘data’). Slide to execute
12. Give it time to load and boot up
13. You should be good to go!
If you don’t like CM 12.1 installing a new Launcher from the Playstore, like Cheetah will make it run smoother. Everything after that is down to you.
Of course, you could flash another ROM via TWRP
The backup below was made via TWRP 2.8.6. This is also attached below. You can install this via a previous version of TWRP as an image. Unzip it first.
Assuming this doesn’t wreck your phone and you like the guide please click Thanks below.
https://drive.google.com/file/d/0ByoLjFrSKxLwc01UUWZBZEQtbWs/view?usp=sharing
https://drive.google.com/file/d/0ByoLjFrSKxLweGhqNGJuVGV1a0U/view?usp=sharing
Related
Hi Guys!
I am trying to root my nexus, unlocked it, installed the right usb drivers, I can see the phone and everything looks right.
Downloaded Superboot for ERE27 with himem enabled and ran this. no problem.
I put the img file on the SD card and when I boot the phone in Fastboot / Recovery it does not find and img files on the SD card.
I tried 2 different cards and also different img files.
When I do this I get first the message no images found than I see the droid with a triangle and a ! in it. - Have to pull the battery.
Ideas anyone?
Thanks
What are you trying to do?
1) you had to unlock the bootloader which enables you to install a new recovery image (which is needed to allow you to install new roms)
2) you had to apply the recovery image Amon RA via a command prompt and a batch file if you use Windows. The phone's USB connection needs to be in development mode and once the batch file executes and successfully finishes you need to reboot the phone.
3) you restart the phone into bootloader mode, use the volume rocker to select the recovery console. If you end up with an andriod and exclamation symbol the Amon RA recovery file was not installed.
4) the new recovery console allows you to clean the SD card. Install roms from the SD card and some other commands. The Roms for the Andriod are in ZIP format and do not need to be unziped. In other words all you need to copy to the SD card is the full ZIP file (approx 75MB) and install that directly from the recovery console.
If your android stays in the booting sequence which is shown as the X with flying little pixels, it's most likely because you did not wipe the device clean first. That item is in the recovery console as well.
Hope this helps. I am just as new to this as you are.
You didn't unzip them did you?
You're trying to root with superboot. Great, but the recovery is not capable of flashing .img files, only .zip updates and roms and such. .img files have to be flashed using fastboot, not recovery, and are flashed from the connected computer.
If you read the superboot instructions from wherever you got the file, you'll see that you have to put the .img in the same directory ON YOUR COMPUTER as fastboot, connect via USB, boot the phone into fastboot, then enter the appropriate command line on the computer to flash the file.
If you've done that, then you are officially DONE with the rooting process.
Also, make damn sure that the superboot version matches the software version on your phone. They're both ERE27, right?
I'm not sure what anosis's post is talking about, but that looks more like the process for installing a custom rom (ie cyanogenmod), than rooting.
To root your phone, you DO NOT need Amon-RA's recovery. You only need that if you want to install custom roms, etc. It wont hurt to have it, as it includes many more functions than the stock recovery, but just to root, you don't need it.
Summary:
If you flashed the superboot.img from your computer via fastboot, your phone is rooted. Done.
You don't need to do anything in the recovery at all for rooting. Only for installing update.zips and custom rom.zips.
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Daboxk said:
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Click to expand...
Click to collapse
It looks like the time when you were locking-unlocking the bootloader, you messed up the recovery. Since your phone can get into bootloader menu, I think you can get out of this issue.
Here is what I would do.
1. Unlock the bootloader.
2. flash clockworkmod recovery using fastboot USB.
3. Download recovery-RA-passion-v2.2.1.img, put it in C:\fastboot\
4. Shut down your phone. Then start your Nexus One in Fastboot mode by holding down the Trackball and press the Power button.
5. Connect your phone to your computer. Open a Command Prompt (Start -> All Programs -> Accessories -> Command Prompt), and run the following commands:
cd C:\fastboot
fastboot devices
fastboot flash recovery recovery-RA-passion-v2.2.1.img
now see if you can get into recovery. If you can, just flash a custom rom using install zip from sd card option in the recovery
I didn't read all the replies but fastboot reads from your PC's disk not the sdcard, unless you are running it through shell or something?
Malfunction " x " appears on the screen !! help me what is going on
Haha... you'll need more information than that if you want real help.
Based on the limited information though I suspect your phone is stuck in a bootloop. I'd hook it up to the PC via USB and check the logcat. Probably something screwed up.. Maybe time to restore your latest backup.
Did you flash any ROM if so, did you clean your Dalvic+REgular Cache
If you don't have an Recovery:
- Connect your Micro SD on PC
- Download and insert on SD the stock ROM of your Nexus One
- Power ON your Nexus with Volume Down Pressed.
- Autmotically Restore Nexus (You should say Yes xD)
At this time, you decide if you want to be root and install other ROM
you better just list your setup info before doing anything
locked/unlocked bootloader
rooted/unrooted
which recovery are you using
what rom are you running stock/custom
what were you doing when this happened
a couple safe things you can do in meantime is to pull battery and reinsert and power on
if it goes back to X, pull battery and DO NOT power on. Hold down the pwr button and trackball at same time and see if you can get into recovery
the third is hold down trackball/vol-/power at same time while X is on screen and see if you can get to recovery that way
if you can't get to recovery you will need to fastboot new recovery, assuming you are unlocked
once you get into recovery do a nandroid if you are rooted
and copy it to pc as a secondary backup
it is possible you may need to try the passimg method in wiki
http://forum.xda-developers.com/wiki/Nexus_One/Guides_&_Tutorials#Unroot_.2F_Restore_your_Nexus
also to do fastboot commands you need usb debugging selected on phone--hope it is
Hello, i have a similar problem with my n1
the phone starts and just shows the nexus X - (waited for 15 min. nothing happend)
i can go to the bootloader / fastboot menu with PWR + (Vol-) but i can not go to the recovery mode. -> the phone reboots and get stuck at the X
the phone is rooted
blackrose / hboot 7.35.5017
radio 5.12.00.08
recovery was ext4
i had a german ics miui rom installed and tryed to install the latest ics miui us rom after it didn't booted the miui us rom i turned the phone off and tryed a few hours later to turn it on to reflash the german ics miui rom.
1.)
i tryed to install a new recovery image ->
recovery-clockwork-5.0.2.0-passion &
recovery-RA-passion-v2.2.1
(still get stuck at the X if i try to go to recovery mode)
2.)
i tryed this one with the passimg.zip but nothing happens if i put in the sd card :/
(with nothing i mean the green text show that the sd card is checking for PASSDIAG.zip and PASSIMG.zip but dosn't found it)
i also tryed:
3.)
erased boot
flash boot from passimg.zip (PASSIMG_Passion_Google_WWE_2.18.1700.1_FRG83_release_signed)
4.)
erased cache
erased userdata
started again with 1.)
5.)
got frustrated and erased system -.-
any ideas?
study it ,thank you
study it ,thank you
Hmm, sorry if its obvious but i have no idea what it could be or what i have to search to find the solution. Would be nice if you could give me a hint. Of course im not asking for a step by step solution. Thank you.
Send from my awesome SE K800i
not sure why you are flashing boot images
do you have a nandroid--copy your sdcard with the nandroid to pc--all of sdcard
are you flashing thru fastboot in command window
did you read my post above on getting to the fastboot screen--can you do that--the one with the 3 androids
pwr/vol-/trackball same time, may take 20-30 seconds
if you can get there, put your recovery image in your fastboot folder on pc, normally tools--assuming you have sdk installed, your phone must have usb debugging checked--I hope
open a command window and change directory to the tools folder or wherever the fastboot.exe file is. Something like:
cd/
cd/ android/android-sdk-windows/tools for me
then on same line type
fastboot devices (it should show your phone H#)
fastboot erase system
fastboot flash recovery recovery.img (or the exact name of the recovery image, checked by right clicking on the img file in your tools folder and looking under properties)
I would use amonra you listed above and check the md5 if possible
hopefully the recovery will flash
if not you can go to the wiki link i posted above and try passimg metthod from there, use correct one. don't add the .zip. Windows will had it automatically.
a side note, DON"T flash different roms without wiping all including System 3 times before flashing--prevents a lot of problems
rugmankc said:
a side note, DON"T flash different roms without wiping all including System 3 times before flashing--prevents a lot of problems
Click to expand...
Click to collapse
thank you very much
i already tryed everything else what you wrote but i didn't wiped 3 times... after erasing recovery partition 3 times i was able to flash a new recovery and it started.
Thanks a lot!
Glad that you got it
Hello everyone!
I tried to restore the stock image using Nexus 4 Tool Kit (both the original one and the Wug's one), and everytime I tried, the script stucked at "writing system".
I manually flashed system and userdata images with Wug's tool kit and everything went well but I only have 5Gb memory instead of 16.
Does anyone know why?
Try this http://forum.xda-developers.com/showthread.php?t=2033692
[HOW-TO] Fix internal storage if 16GB now shows 8GB
Sent from my Nexus 4
OP...
In future, don't use a toolkit. Do it yourself
I'm having a similar problem to the OP - I'm trying to do a factory restore, and am unable to flash the "system" image. I can't boot, recovery mode won't work anymore (I get a red warning sign instead)...
I think all of this has to do with me being naieve and following a youtube video instead of the CM wiki to install CM 10.1.
How can I unbrick my phone?
4OnTheFloor said:
I'm having a similar problem to the OP - I'm trying to do a factory restore, and am unable to flash the "system" image. I can't boot, recovery mode won't work anymore (I get a red warning sign instead)...
I think all of this has to do with me being naieve and following a youtube video instead of the CM wiki to install CM 10.1.
How can I unbrick my phone?
Click to expand...
Click to collapse
When going into recovery the warning sign is the splash screen for stock recovery. This likely means that you have not yet flashed a custom recovery yet, which is necessary to flash CM. First read this guide to unlock the bootloader (if you havent already), then flash a custom recovery (preferably TWRP). After you have installed the recovery, download CM as well as the latest gapps package and place them somewhere on your internal sd. Boot into recovery and go to the wipe menu, then swipe to factory reset. Finally flash the rom and gapps, and then reboot.
4OnTheFloor said:
I'm having a similar problem to the OP - I'm trying to do a factory restore, and am unable to flash the "system" image. I can't boot, recovery mode won't work anymore (I get a red warning sign instead)...
I think all of this has to do with me being naieve and following a youtube video instead of the CM wiki to install CM 10.1.
How can I unbrick my phone?
Click to expand...
Click to collapse
if you are doing a factory restore and DONT need to flash everything individually than don't. yes its good to know how to do it manually but if your flashing everything back just use the script that google provides.
reboot to bootloader/fastboot and run the flash-all.bat file and its all done for you. no toolkits no playing with commands that you dont know properly etc.
if you dont know how to do it right pick the least complicated option.
noobdeagle said:
if you are doing a factory restore and DONT need to flash everything individually than don't. yes its good to know how to do it manually but if your flashing everything back just use the script that google provides.
reboot to bootloader/fastboot and run the flash-all.bat file and its all done for you. no toolkits no playing with commands that you dont know properly etc.
if you dont know how to do it right pick the least complicated option.
Click to expand...
Click to collapse
I am using the .bat file... I've also tried the toolkit, and both appear to use the same basic procedure, and they stop at "writing system" no matter what.
Does anyone happen to know how the .bat file and toolkit get access to the phone? ...because I can't see it in adb (I'm guessing it's because I can't boot the phone.) However I can get into fastboot and recovery modes on the device.
I cannot get the device (nexus 4) to boot or connect in ADB mode to my computer. What can I do??
UPDATE - PROBLEM FIXED
I un-bricked my phone
SOLUTION this is what worked for me, your mileage may vary
Install ADB drivers, etc. from Android SDK (google how to do this)
Flash custom recovery (can be done easily with Nexus 4 Toolkit here on XDA) - I used TWRP Touch Recovery.
Once that is done, shut the phone off completely and boot into Fastboot (hold volume down and power)
Use volume keys to select Recovery Mode, then hit Power
In recovery mode:
Wipe > Advanced Wipe > Check off the box beside "System" > Swipe to Wipe
Go back to recovery mode main screen:
Wipe > Format Data > Follow the instructions on the screen
I think this step is what did it. When having problems with partitions, just format everything and start over
Now we should be able to write to the System partition, meaning you can flash a ROM and get your phone to boot again.
Follow the rest of these instructions to quickly flash the stock Android image from Google onto your phone.
Go back to recovery mode main screen, once again:
Reboot > Bootloader > Follow any additional instructions it gives you
Download Google Nexus 4 factory stock image "occam" (Google it)
When that is downloaded, open it with 7zip. Inside there are some files, one of which is called image-occam-jdq39.zip. Inside are some images - unzip those as well. You'll need the system.img file in a bit...
Using Wug's Nexus Root Toolkit (Google it - install it on your Windows PC):
Open the program
Launch advanced utilities
Hit the System button to permanently flash to System partition. Hit "ok" on the window that pops up.
Find the system.img file I mentioned back on step 10 and select that, when prompted, and open it.
If all went well, your device will now boot into the stock Android ROM.
noobdeagle said:
if you are doing a factory restore and DONT need to flash everything individually than don't. yes its good to know how to do it manually but if your flashing everything back just use the script that google provides.
reboot to bootloader/fastboot and run the flash-all.bat file and its all done for you. no toolkits no playing with commands that you dont know properly etc.
if you dont know how to do it right pick the least complicated option.
Click to expand...
Click to collapse
I too am stuck at writing system. I"m not sure what you mean when you said "run flash-all.bat". Where do I get that?
Thanks.
Soundchasr said:
I too am stuck at writing system. I"m not sure what you mean when you said "run flash-all.bat". Where do I get that?
Thanks.
Click to expand...
Click to collapse
The system takes awhile to write, how long have you guys wait before you say its "stuck"?
Sent from my Nexus 4 using Tapatalk 4 Beta
About 20-25 minutes.
Yea, that's way too long.
Sent from my Nexus 4 using Tapatalk 4 Beta
Stuck, but working
I was flashing the 4.3 image using the included flash-all.bat (but I edited it to remove -w parameter so that it wouldn't wipe my data).
In the 'writing system' step, the command window got stuck. In the phone screen, at the bottom, it said 'writing' for a while and then that also went away. I waited for ~40 min, and still the command window was at 'writing system', so I closed the command window, and booted my phone by selecting start from the bootloader.
And voila! It worked. Booted in under a minute, the flash was a success, I got JB 4.3 without losing any of my data.
Lost my root and custom recovery though. But I knew that would happen. Gonna try SuperSu for 4.3 now, after flashing TWRP.
Had the same problem, tried everything! With my tiny powers, but it kept stucking at "writing system" . I thought that I bricked the device, so for the last hope, I installed WugFresh's Nexus Toolkit and did a Fast Stock + unroot. It Installed everything flawlessly! I'm gonna donate to that guy! He's a godsend savior.
Hi, I was switching rom cuz of many errors and I stucked on TWRP. Im able to enter download mode and adb and internal storage via PC. Whenever Im trying to flash new ROM twrp just restarts. I search whole the forum and no one of guide work for me. Additional full wipe and hard reset doesnt remove previous system. When Im connecting to lg mobile flash he says that I have still OptimusROM. Please help me
@edit:
After a few hours I find a simple solution. If u got the same situation like me just lanuch adb via cmd and write "adb reboot fastboot". After u can restore stock with LG flash tool. Just be sure that u have .kdz file in the same direction.
Xematos said:
Hi, I was switching rom cuz of many errors and I stucked on TWRP. Im able to enter download mode and adb and internal storage via PC. Whenever Im trying to flash new ROM twrp just restarts. I search whole the forum and no one of guide work for me. Additional full wipe and hard reset doesnt remove previous system. When Im connecting to lg mobile flash he says that I have still OptimusROM. Please help me
@edit:
After a few hours I find a simple solution. If u got the same situation like me just lanuch adb via cmd and write "adb reboot fastboot". After u can restore stock with LG flash tool. Just be sure that u have .kdz file in the same direction.
Click to expand...
Click to collapse
Given what you're saying, I'm guessing you're using at least 1 f2fs partition in the custom rom.
This has caused TWRP to panic and reboot for a few people (myself included) when trying to reformat f2fs partitions. The only way to fix that is like you're doing, or wiping the affected partitions back to EXT4, then going back to f2fs if you REALLY want to use it. The reason that this would cause the reboots on install, is because one of the first things most roms do is format cache.
Hello everyone,
I have recently unlocked the bootloader on my Nokia 6.1 plus, and rooted it. I then went ahead and installed TWRP ( App install method - found in the twrp website ). However after I rebooted my phone has been stuck on the TWRP splash screen , I Tried going to download mode , and that just got me back to the twrp splash screen. I turned off the phone and powered it on again , same result . Whatever I do it just keeps going back to the TWRP splash screen .. What is even worse is that my device can not be recognized by my pc while stuck on the splash screen , thus I can not use ADB or Fastboot ...
I am feeling really hopeless and stuck , Help would be much appreciated!! Thanks
Now, dissemble the device and enter edl mode
Sent from my Nokia 6.1 using Tapatalk
MaxTurner771 said:
Hello everyone,
I have recently unlocked the bootloader on my Nokia 6.1 plus, and rooted it. I then went ahead and installed TWRP ( App install method - found in the twrp website ). However after I rebooted my phone has been stuck on the TWRP splash screen , I Tried going to download mode , and that just got me back to the twrp splash screen. I turned off the phone and powered it on again , same result . Whatever I do it just keeps going back to the TWRP splash screen .. What is even worse is that my device can not be recognized by my pc while stuck on the splash screen , thus I can not use ADB or Fastboot ...
I am feeling really hopeless and stuck , Help would be much appreciated!! Thanks
Click to expand...
Click to collapse
You shouldn't have installed TWRP on a A/B device let alone install it via the app. It's okay, We're here to help.
If you have OSTLA in your PC, Just open it up and load all files and select to flash the stock ROM. Select Normal Download/Erase User Data options and if the option to Chech AP status is enabled, Disable it. Select on start or the option to flash stock ROM.
Power off your phone completely. If you can't, Then press the volume+ button and power button. Once the screen goes off, Immediately connect phone to PC.
Phone should now reboot into download mode and stock rom should start flashing. Then it's just a matter of waiting for it to flash and reboot.
CarbonGTR said:
You shouldn't have installed TWRP on a A/B device let alone install it via the app. It's okay, We're here to help.
If you have OSTLA in your PC, Just open it up and load all files and select to flash the stock ROM. Select Normal Download/Erase User Data options and if the option to Chech AP status is enabled, Disable it. Select on start or the option to flash stock ROM.
Power off your phone completely. If you can't, Then press the volume+ button and power button. Once the screen goes off, Immediately connect phone to PC.
Phone should now reboot into download mode and stock rom should start flashing. Then it's just a matter of waiting for it to flash and reboot.
Click to expand...
Click to collapse
I had a problem in that my device would never be recognized by my pc even when i finally manage to put in download mode, However after many days trying I was finally able to do it , and to use OSTL.... so thank you!!
I am wondering now how I will do the thing i wanted from the start which is to flash a kernel if i shouldn't use twrp?
MaxTurner771 said:
I had a problem in that my device would never be recognized by my pc even when i finally manage to put in download mode, However after many days trying I was finally able to do it , and to use OSTL.... so thank you!!
I am wondering now how I will do the thing i wanted from the start which is to flash a kernel if i shouldn't use twrp?
Click to expand...
Click to collapse
So to my understanding what you want to achieve is flash a custom kernel on stock rom. And after you messed up your stock recovery by installing twrp, if you have flashed stock rom using ostla then follow these steps.
First without tampering anything finish an ongoing/pending ota/sp update cause after you install custom kernel you phone won't be able to install OTAs. The last sp is of june so install that.
Now coming to installing the kernel-
*Place your twrp and kernel zip file into your adb folder*
1. Setup usb debugging and connect your device normally to your pc, check if the device is communicating with pc type in "adb devices" and allow on your phone for authorisation.
It should reply with your serial on cmd window.
2. Type in "adb reboot bootloader" that should put your device in download mode.
3. Type in "fastboot boot twrp.img" (replace twrp.img with whatever your twrp image file name is)
4. Go to advanced and select adb sideload, swipe to start.
5. Now move to your cmd window and type in "adb sideload kernel.zip" (replace kernel.zip with whatever your kernel zip file name is)
Wait for the process to finish
Now press home go to wipe>advanced wipe select dalvik cache and swipe to wipe
again press home and select reboot, select system
Now final important step
6. don't swipe, select "do not install twrp"
D-Mi said:
So to my understanding what you want to achieve is flash a custom kernel on stock rom. And after you messed up your stock recovery by installing twrp, if you have flashed stock rom using ostla then follow these steps.
First without tampering anything finish an ongoing/pending ota/sp update cause after you install custom kernel you phone won't be able to install OTAs. The last sp is of june so install that.
Now coming to installing the kernel-
*Place your twrp and kernel zip file into your adb folder*
1. Setup usb debugging and connect your device normally to your pc, check if the device is communicating with pc type in "adb devices" and allow on your phone for authorisation.
It should reply with your serial on cmd window.
2. Type in "adb reboot bootloader" that should put your device in download mode.
3. Type in "fastboot boot twrp.img" (replace twrp.img with whatever your twrp image file name is)
4. Go to advanced and select adb sideload, swipe to start.
5. Now move to your cmd window and type in "adb sideload kernel.zip" (replace kernel.zip with whatever your kernel zip file name is)
Wait for the process to finish
Now press home go to wipe>advanced wipe select dalvik cache and swipe to wipe
again press home and select reboot, select system
Now final important step
6. don't swipe, select "do not install twrp"
Click to expand...
Click to collapse
This might sound like a stupid question but I am a major newbie when it comes to this,
Right now i managed to compile a custom kernel and I have a boot image along with the kernel, so to get the kernel.zip do I just zip up all these files? also I read that I could simply flash the image by rebooting to my bootloader and then using " fastboot flash boot boot.img " would this work , and if so does this mean i don't need twrp...
Thanks again for the help , it is much appreciated
MaxTurner771 said:
This might sound like a stupid question but I am a major newbie when it comes to this,
Right now i managed to compile a custom kernel and I have a boot image along with the kernel, so to get the kernel.zip do I just zip up all these files? also I read that I could simply flash the image by rebooting to my bootloader and then using " fastboot flash boot boot.img " would this work , and if so does this mean i don't need twrp...
Thanks again for the help , it is much appreciated
Click to expand...
Click to collapse
If you just want to flash your custom kernel there's no need to flash a boot.img if you've a running rom installed. You can flash the kernel.zip it via twrp or adb sideload via twrp.
Sorry for the late reply, if you have a bootloader-unlocked 6.1 Plus you should join Nokia 6.1 Plus community on telegram you'll get much faster response from the community regarding your device ?