Hi there, hoping someone can help.
Had my BLL-L22 working perfect and had carbon rom working, till one day it just decided to ask for factory reset. From there something crazy happened and my recovery partition aswell as system partitions were completely dead, fastboot didnt work either.
I used the NDIT tool to recover using the jumper method and i got my 6x booting once again, except on the NDR90 rom, anyhow everything picks up now and works, but now my model is stuck on generic_a15 instead of bll-l22, whenever i flash oeminfo it says device not verified and cant boot,
Anyhow - gone ahead and installed carbon ROM again, tried AOSPE too, same thing, both sims wont pick up, and wifi won't turn on, when i restore stock - everything boots fine.
It worked prior to the recovery, now no aosp rom will pick up my imei's or wifi, but stock does. any one got any ideas i could try to get wifi and sims working?
Thanks!
Try flashing full stock BLL-L22 firmware with HuRUpdater and then flash custom ROM again. Vendor partition must be okay in way to use some function in other ROMs than stock one. Plus, flashing full firmware through HuRUpdater should fix the "generic_a15" model name mismatch.
Related
Please Help
I was in miui ROM then I tried flashing Metallium ROM, after I flashed it, it booted up but, it wasn't restoring my previous apps, so I skip that part, but then when I got to the home screen I wasn't able to access my stuffs in my phone memory.
So I thought maybe I need to change the data to f2fs, so I went to the recovery and did and flashed the Metallic ROM again, but this time it didn't boot at all, there was a bootloop and I could get past the start up screen.
I tried my older ROMs the one that I had, but it's all giving me the same response now, I have switch before but I never have had this problem. Please help, how do I flash other lollipop ROM again.
Maybe changing to f2fs and doing a factory reset. If that doesn't help, flash stock ROM via fastboot.
kennylrmsailo said:
Please Help
I was in miui ROM then I tried flashing Metallium ROM, after I flashed it, it booted up but, it wasn't restoring my previous apps, so I skip that part, but then when I got to the home screen I wasn't able to access my stuffs in my phone memory.
So I thought maybe I need to change the data to f2fs, so I went to the recovery and did and flashed the Metallic ROM again, but this time it didn't boot at all, there was a bootloop and I could get past the start up screen.
I tried my older ROMs the one that I had, but it's all giving me the same response now, I have switch before but I never have had this problem. Please help, how do I flash other lollipop ROM again.
Click to expand...
Click to collapse
Anyone out there? Need help desperately.
Anyone?
samuelcr93 said:
Maybe changing to f2fs and doing a factory reset. If that doesn't help, flash stock ROM via fastboot.
Click to expand...
Click to collapse
Yeah that might work but I'm kinda looking for a solution where I don't have to flash the stock again because I lost all my moto g stuffs some months back.
And another thing is that when I flash MIUI its working fine again and I'm able to access all the file in my phone storage also. Any suggestions?
Mmmm if you are using TWRP you could connect the phone to the PC and make a backup while you are in recover mode. Then format again data partition to f2fs and make a factory reset including internal storage and finally flash your ROM and restore your files.
But if that is not working then the only option is flashing Stock ROM
If MIUI is still booting it means that your data partition is still ext4
hey y'all i have a 6045i US and it keeps bootlooping it all started by flashing CM 12.1 4/03/16 verison by the marionetteso i also flashed gapps xposed and root so it gave me the bootloops so what i did is wipe data factory reset nothing worked so i flashed another ROM wipe data everything and flashed bootloop fix kernel and nothing,same results im at the homescreen and im doing things and bootloops from there even recovery rebooted alot lol im not sure why so i flashed another older verison of it (i risked btw) and it worked so with that recovery i flashed a TWRP backup from one of the threads to stock ROM wipe data etc. and nothing same results!!! bootloops from homescreen so if theres another way to fix id appreciate it so much a clean install as in out of the box also i tried the alcatel upgrade app and nothing everytime i shut down the phone and plug the USB it just turns on for some reason bootloader works still with fastboot commands so i dont know whats going on this is my first issue with this phone,thank you
EDIT: fixed i finally got the alcatel app to work mods please close this thread
I did a quick look at the Q&A and didn't found anything similar to my problem. I had an 6.0.1soak stock rom, tried a custom rom didn't liked and tried to go back to my stock rom, TWRP started giving me erros like: Cant mount /modem can't mount /firmware but ok i made it boot at least then i had problems because if you PIN your lockscreen you're screwed, gotta go delete that DB file which i did but now WIFI is broken and settings force close. Is there any way to restore my stock backups with TWRP or i need to flash a stock image in RSD lite and start everything again ? I tried to restore backups then factory reset but WIFI still dead...
I apologize if we already had this issue on the forum, but i wanted to take any other options avaliable before setting everything up again from scratch, thanks folks.:cyclops:
E398 said:
I did a quick look at the Q&A and didn't found anything similar to my problem. I had an 6.0.1soak stock rom, tried a custom rom didn't liked and tried to go back to my stock rom, TWRP started giving me erros like: Cant mount /modem can't mount /firmware but ok i made it boot at least then i had problems because if you PIN your lockscreen you're screwed, gotta go delete that DB file which i did but now WIFI is broken and settings force close. Is there any way to restore my stock backups with TWRP or i need to flash a stock image in RSD lite and start everything again ? I tried to restore backups then factory reset but WIFI still dead...
I apologize if we already had this issue on the forum, but i wanted to take any other options avaliable before setting everything up again from scratch, thanks folks.:cyclops:
Click to expand...
Click to collapse
[ROM][6.0.1][Stock][Odexed]MPG24.107-70.2 Brazilian 6.0.1 for XT1254[TWRP Flashable]
http://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
If you flash it you have to be rooted and have TWRP installed. It's pure factory Marshmallow for ANY Quark -- XT1254, XT1250, XT1225. It will use whatever radio you already have installed.
iiWoodstocK said:
this ROM is just factory Marshmallow with a modded build.prop. I didn't include any radio in the .zip, so it uses whatever is currently on the device. Aside from my build.prop tweaks, this ROM is even usable for Brazilian XT1225 users, but the device will say it's a Droid Turbo and contain useless CDMA build.prop lines.
Click to expand...
Click to collapse
Thanks for the help, i installed and configured everything, but i just saw now that my 3G isn't working lul! I found this image on the internerd "XT1225_QUARK_RETBR_6.0.1_MPG24.107-70.2_cid12_subsidy-DEFAULT_CFC.xml" flashed and well got the internet working.
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
wahlmat said:
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
Click to expand...
Click to collapse
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(https://dl.twrp.me/bacon/).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware: https://drive.google.com/file/d/0BxysuRdzsJeWeW9JbTNwaUJKb1E/view?usp=drivesdk
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(opengapps.org)(optional).
Reboot.It should boot fine now.
Good luck!
Mr.Ak said:
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(Can't post links withing 10 posts apparently...).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware:
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(Can't post links withing 10 posts apparently...)(optional).
Reboot.It should boot fine now.
Good luck!
Click to expand...
Click to collapse
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
wahlmat said:
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
Click to expand...
Click to collapse
I'm glad you got it up and running.
Here are some FAQs:
What is a Firmware? What is Modem?
- Firmware is the whole package of proprietary partitions of your device, modem itself is a NON-HLOS file responsible for your device's communications over Wi-Fi, Mobile Networks and other such stuff.
So what is the difference between firmware and ROM then?
- Firmware is the responsible partition for IMEIs, the modemst partitions hold your IMEI, persist holds your Mac addresses etc.
ROM is only a combination​ of system.img and boot.img (kernel)
What to restore if I loose my IMEI?
- Both the modemst partitions (IMP: considering you took a backup of them before)
What is the default firmware? (default= firmware which comes with the latest CM/ LineageOS 14.1 weeklies)
- c6-00241
Thanks a lot, once again
Help!
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
HisMuse said:
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
Click to expand...
Click to collapse
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
wahlmat said:
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
Click to expand...
Click to collapse
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
HisMuse said:
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
Click to expand...
Click to collapse
Yes you do. You need that + some software. Check out some "install custom recovery oneplus one" guides, you should be able to find something. Are you on Mac or Windows?
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
HisMuse said:
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
Click to expand...
Click to collapse
Download the Samsung ADB driver or whatever it was called, then flash a new recovery for it. There are multiple guides for doing that. After that you should be able to transfer your files to your pc while being in recovery mode
Hello,
I have an unlocked & rooted S7 herolte, on which I flashed custom ROMs time to time. Last time I was switched from
TGP_G93xx_XXU5ESD2_v2.9.1
to
[Samsung][ROM][PIE][9.0][06-July-2019][S7_S7E_F_FD][Note_FE_Port][v12]LightROM.zip
but I didn't liked it, and tried & failed to return to the TGP ROM, as the phone goes into bootloop after the setup, even if I wipe everything not just factory resetting the phone.
The bootloaders appear the same "5" (5ESD2) so any clue(s) welcomed how can I restore the previous stage - even complicated ones.
Thanks!
Finally I somehow managed it.
Tried to flash older stock roms (BL AP CP CSC HOME) with odin 3.12x & with 3.13.3 but failed.
Then wiped everything, (TWRP) flashed an old Hydra rom, which surprisingly started to boot, then it said, data partition error.
Wiped again everything, then repaired all partitions (file system repair) which allowed it, then I've tried TGP 2.9.1 and it succesfully booted & runs.
It asked for change to (it's) latest modem & bootloader, so maybe that did the trick, but finally...
Congrats. I'm curious about your experience with the LightROM PIE port, and why you didn't like it.
download stock ROM and ODIN 3.13 and flash only the AP file of the stock ROM in ODIN and then it will boot, if it doesnt boot just flash CFAUTO ROOT or majisk and it will boot
Droiderat said:
Congrats. I'm curious about your experience with the LightROM PIE port, and why you didn't like it.
Click to expand...
Click to collapse
For me The Galaxy Project is the gold standard ROM (adblock, reboot to recovery & others, sound mods, etc) and even if I try any other ROM, I have to feel myself at home after a few swipes. The LightROM would be okay, but the fact, that it couldn't restore any of my backup after I set up my google account on the phone was the deal breaker for me. The way google backs up the data when I manually try to get it do that is a PITA, losing it all for any new ROM isn't worth it for me.