Related
Hello,
I have a very strange problem with my phone.
After installing the new ubuntu-touch release on the 17th October and reflashing paranoid android, I can't get any signals on pa (no imei, no baseband). The strange part is, if i install the stock rom, cyanogenmod, aokp, I can get these signals and it will display my imei.
The other thing is, in bootloader it displays the correct baseband and bootloader. (i have installed the one from date I have bought my phone and the one from the thread about paranoid android 3.99 RC2). I also have tried PA 3.99 RC 1 the last version worked with signals.
The first time I have installed ubuntu-touch I had signals and in the recovery i got two new mountpoints firmware and persist. I reinstalled ubuntu-touch and now there are also no signals. I can remember I also have formated firmware and persist. So may this could be the problem. At least I have decided to follow this guide:
http://forum.xda-developers.com/showthread.php?t=2347060 ([GUIDE]99% working unbrick method aslong you can get into download mode )
The problem persist, but the two mountpoints disapeared. (FYI: I have a Nexus 4 16 GB Model)
May one of the mountpoints were not restored correctly by this guide. May someone can backup his firmware mountpoint and can tell me where i have to restore it, because i think the whole /dev/block/mmcblk0 will be restored by this guide, if not so may the persist partition could be the problem and the firmware partition was created by ubuntu-touch and is not needed by android roms. (But I'am not into any android specific partition layouts)
I have backuped the efs "m9kefs1" and "m9kefs2" now. And the Phone runs now on the newest build of cm.
May someone could help me or have an usefull idea. But I can live without ubuntu-touch and paranoid android, but I really like the features of paranoid android.
Best regards
Richard
I assume you tried it with both recoveries just for trouble shooting. Also I know this doe not effect IMEI but did you try flashing radio after PA? Also did you have a backup of PA on your phone and did you try to restore from backup
Ubuntu-touch recovery, its still the same as clockworkmod (if you mean that with both recoveries). I only used cwm to wipe data and install roms.
I also have tested to install radio and boot after pa, without success. In recovery I can see persist and firmware, may it is something pa specific.
I had a backup, but I wiped it. I never thought a backup is a cleaner solution than a fresh rom installation. I thought its only for saving data.
[Solution] [Solved]
The Problem is the newest CWM as mentioned in this thread ([EXPERIMENTAL] Semi-official builds of Omni):
http://forum.xda-developers.com/showpost.php?p=46511999&postcount=4
The solution is to downgrade CWM, you could do this by:
Code:
http://clockworkmod.com/rommanager
Chose Nexus 4 and copy the link of the version you want to download:
Code:
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-[B]6.0.4.3[/B]-mako.img
Than change the version number to a lower version, like this:
Code:
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-[B][U]6.0.3.1[/U][/B]-mako.img
Go to fastboot mode and erase userdata: (This will delete your private data)
Code:
fastboot erase userdata
Than lets write it again:
Code:
fastboot -w
Go to recovery mode, wipe and format all partitions, at least install paranoid android and reboot to system. Now the services should be back.
May you could skip the fastboot steps, but I stuck at a very long boot (I interpreted this as a bootloop and decided do format all partitions with cwm, install pa and reboot again. That worked for me)
Glad you fixed it but thats why I asked you if you tried both recoveries... I also know some versions of TWRP had that issue but its since been resolved in the latest version. Most have more success and less issues with TWRP not CWM...
Hi,
a few days i deviced to manualy flash 5.0.2 an my old n7.
flashing 5.0 already made many problems.
so i hoped 5.0.2 would be easier.
i wasnt -.-
i can flash bootloader, recovery but not system. when i flash system (fastboot flash system system.img, all drivers corectly installed) it lasts ours until my pc says something new like "too many links" or so. but not every time it comes to an error message. sometimes nothing happens (waited 2 days!)
the n7 it selfs dont react then.
at flashing 5.0 it helped me to change the filesystem and change it back. at 5.0.2 nothing helps. also cant flash back 5.0
bootloader is 4.23.
has anybody an idea?
What filesystem are you trying to use? Keep it at ext 4 until you get the 5.02 system flashed. Try a fastboot format system before flashing again.
Sent from my Nexus 7 using XDA Free mobile app
I switched to ext3 and instantly back to ext4 . Never tried to flash on an other filesystem.
The format command I will try
i love you
this is embarrassing for me. i tried everything i knew. i also formated the system partiton in recovery. but to format it via fastboot doesnt come to my mind
So I take it that formatting system with fastboot allowed you to successfully flash system.img? I hope you have your N7 up and running on 5.02.
Yes you're right.
I flashed 5.0.2 . So far so good.
But it won't install apps. So I wiped the cache and now I have a bootloop today after work I will look after that. But I'm happy that I can flash normally
I have 6p since last year 6p is a fantastic phablet , it's been a great experience until yesterday , I was chatting with someone and suddenly everything freezes and then it restarts and stuck on Android logo and restarts again ... And this continues ,so somewhere I read that it because of Android n so I flash latest MARSHMALLOW (MTC20L) factory image and luckily it BOOTS up ,but The real problem is when every I flash any version of android N It starts DOING BOOTLOOP ,, I wanted ANDROID N , so someone know any way to flash it without bootloop ,, help !!!
First off, you could have provided a lot more detail about exactly how (and what) you flashed without shouting. Your post for help comes off like a panicked rant. What is your current configuration... stock rom? rooted? stock kernel? stock recovery? encrypted? My advice would be to stop flashing your device for now. If you haven't done so already, confirm that your bootloader is unlocked. Next, make full partition backups including EFS, and store them somewhere off the phone. Now you can start reading on how to flash correctly with the least amount of risk.
Sorry for bad English
My 6p's bootloader is unlocked and I was using it with latest stock Android 7.1.1 with ElementalX since last month then years suddenly it freezes and stuck on boot loops then I flash Android 6.0 latest and it works fine on it ,and doesn't goes under boot loop but when ever I flash Android 7 it stuck on bootloops ,
I have a full TWRP backup of my android developer preview 4 ,I also restored it but still same bootloop issues with android 7 Roms , I also tried latest factory image of Dec,16 android 7.1.1 ,but still no luck
Once again, short on details.... how did you "try" the factory image? Since you already had 7.1.1 running well for the last month, you could have just done a full factory reset from stock recovery (not TWRP) to rule out personal apps and your setup. Since you have some backups and are unlocked, use ADB to first fastboot format userdata and cache. Then fastboot flash the full NMF26F image- not OTA. Let the phone stabilize first and test it before installing all your applications.
Hi guys, been using my rooted but otherwise stock OOS rom with TWRP and Magisk for the past few weeks. Today I decided to take the plunge and try either the Lineage OS or Resurrection Remix roms.
I'm using the latest OFFICIAL TWRP.
So I decrypted following the instructions to flash "no-verity-opt-encrypt-5.1.zip", then format data. All went well, so I then sent over the ROMS I wanted to try out. I started with the official ResurrectionRemix. Bootloop. Then the unofficial LineageOS. Bootloop.
Ok, well I guess I'm not gonna get to use any of the cool new OS's for awhile. I'll install the full stock firmware zip so I can have a working phone again. Bootloop.
Now when I say bootloop, the phone is booting to the BootAnimation and just repeating it. It shows the proper boot animation for whatever zip I have installed (resurrection/LOS/OOS), but it stays on there for up to 20 minutes before I have to hard reboot to the recovery again.
I decided to install the stock recovery trying a few methods. I first tried the ALL-IN-ONE tool. It said it flashed the recovery fine, so I booted to the recovery and after staying on a black screen for too long, the language options came up and I sighed a breath of relief. But before I could select English with the volume buttons, it rebooted by itself. It did this again when I manually entered recovery. So I figured maybe the tool flashed the wrong version, so I googled stock recovery for OnePlus 5, I found a few random links for stock recoveries for the OP5 and flashed them, but they more or less do the same thing or not boot at all.
I've tried changing the filesystem for both Data and System using any combinations of EXT4 and F2FS. Everything results in boot animation bootloops.
I have been flashing Roms since the Samsung Galaxy S3 and every phone since and never had any problems.
Currently when trying to install the stock Full OOS official zip with TWRP, the phone won't even go to the boot animation, it only goes to a black screen with the top LED in a light blue color.
I have also tried every version of TWRP there is for the OnePlus 5. Unofficial, Official, 3.1.1-0 and 3.1.1-1.
So I guess my question is....What filesystem is each partition supposed to be on and for which OS?
Lineage based:
System: ?
Data: ?
OOS Based:
System: ?
Data: ?
And any ideas on getting my phone running again?
And anyone have an official confirmed working version of the stock recovery? The one from ALL-IN-ONE TOOL doesn't work for me. It loads the language selection, then the screen goes black with a light blue LED on the top of the phone.
Actually I'm getting that on some roms instead of the bootanimation, like FreedomOOS. What does it mean when you have a black screen and a white LED?
Man, I really thought I was getting somewhere. If I boot into TWRP, change the Data partition to "F2FS", then flash the stock recovery, the stock recovery will boot, however, when inside the stock recovery and I try to flash the stock zip, it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
Ok, I have the official stock recovery from the OnePlus site, but still can't use it. Here is was happens depending on how I left it with TWRP:
System: F2FS
DATA: F2FS
- Stock recovery will load after some time, freeze, then the screen goes black with white LED on top.
System: EXT4
DATA: F2FS
- Stock recovery loads fine, I can go through the settings and install from SD card, but when I do it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
System: EXT4
DATA: F2FS
- If I try to flash stock rom through TWRP, it just boot loops on the animation forever.
I have now also tried flashing the stock boot.img, but no difference.
I have 2 things you can try!
First, replace the bootloader with stock and do a factory reset:
1. flash the stock recovery over
2. then in fastboot mode enter, fastboot oem lock (This forces the phone to wipe cache and data, and also do a complete reset)
Did it work? if yes YAY if not go to Second!
Second if your system.img is ****ed up you have to replace it!
Download the newest version of the stock rom from oneplus link here
Unpack it
research how to use an extractor to convert the system.new.dat to system.img
once thats completed enter fastboot mode and flash the new system.img over with Fastboot flash system system.img
now go into recovery and do a factory reset and wipe cache, and dalvik
Please reply back wether or not this work
"Ihave 2 things you can try! First, replace the bootloader with stock and do a factory reset..."
Is the bootloader simply the boot.img?
After doing the first thing, it simply says that the device is corrupt and will not boot. But it is locked again.
But I will have to unlock it again to do any further flashing.
Hmm, I think I may have gotten it. After unlocking again, flashing the stock recovery and boot.img, then locking again and wiping in the stock recovery, I have finally booted into the stock rom.
I still have no idea what went wrong, and I really want to know, so that in the future I can flash other Roms, like LineageOS.
I mean, I followed the steps exactly.
If it says the device is corrupt it simply means you got something else besides stock rom.
So now unlock it and try the system.img instead
It was because I still had TWRP with the stock rom.
I got it working though, thanks for your help.
Do you have any idea on what might have went wrong when trying to flash the lineageOS based roms and why it got messed up so royally?
Great to hear you fixed it ^_^
Probably some minor bug, if you wanna try installing lineageos again use the 3.1.1 TWRP build that supports backups and do a full backup so you don't have to go thru all this again
---------- Post added at 12:17 AM ---------- Previous post was at 12:13 AM ----------
Not really just try again but remember to use TWRP 3.1.1, as 3.1.0 don't support backup and probably have been part of your problem
If your trying again and gets it successfully installed could you do me a favor and test if Drivedroid works on it? And pm me the result, I'm looking for a rom where Drivedroid will work... Haven't found one so far
You know, I did do a backup with the OFFICIAL TWRP, but it also resulted in a bootloop. I made the backup after decrypting, so I don't know why it bootlopped.
https://forum.xda-developers.com/oneplus-5/development/rom-unified-lineageos-7-1-2-t3635483
Is this the one you tried installing?
I tried like every ROM at one point yesterday, but I think I started with
https://forum.xda-developers.com/oneplus-5/development/rom-resurrection-remix-n-7-1-2-t3636578
Did you remember Gapps?
Also in some cases its better not to root before you have the custom rom running, you usually only need a custom bootloader like TWRP
Yeah, I tried with Gapps, and I never rooted before first trying to boot.
As of yesterday Ressurrection remix, released the first official stable build so try again your should'nt have any problems if you follow the guide 100%
Ever find a solution? I'm stuck here now. Can't get any ROM to boot up, they all get stuck on the boot animation
Bump. I am also stuck in this state
Hi guys,
so I am running into a strange issue: I can't flash any ROMs in recovery anymore.
I switched to Pixel Experience Q from xiaomi.eu's MIUI ROM ~1 week ago without wiping internal storage, so I ended up not being able to use TWRP as I was faced with a password prompt that accepted none of my passwords (current, previous or default_password, etc.). So when an update for PE came I thought "okay let's get this over with now" and did a complete wipe including /data/media from OrangeFox recovery - so far so good.
Now I transferred back the new ROM zip and wanted to proceed flashing it.
Result: Error 7 Failed to update system image (E1001)
Confused by this I went back to the previous version's zip, but the same error comes up.
Even more confused I downloaded all kinds of ROMs and every single one comes up with this error.
I tried
another full wipe
mounting/unmounting system before flashing
MIUI, Android 10, Android 9 ROMs
Different versions of TWRP and OFR
Even different firmware packages
Removed assert and abort lines in the updater-script (which results in skipping the flashing of the system image and then failing at vendor)
Flashing by adb sideload
So the only thing getting me back to a working phone is flashing a fastboot ROM. That works.
Even after doing that, flashing back TWRP/OrangeFox, wiping and flashing a ROM the same error comes up again. I also checked the MD5 hash for my files. They are fine.
I am at a loss of ideas at this point and no solution I found helped. I hope you guys can help me. Thanks in advance. :-/
Well, scratch that, I guess.
After hours of troubleshooting somehow it's working again now.
So for anyone who gets this issue:
Flash a fastboot ROM and...go to sleep and try in the morning.
I'm facing the same problem now.. I think after trying many times its a flash problem, because when I flash over fastboot sometimes stick on 5/7 and others 3/7 etc.. well its a xiaomi is something to expect.
Format Data partition, not just wipe, this should fix those kind of issues.
This.
After more xiaomi devices and more flashing I can definitely say this is the fix.
This.
After more xiaomi devices and more flashing I can definitely say this is the fix.
Try transferring the ROM using a USB 3.0 port. Worked for me...
I am facing the same problem. Can you help me?