Related
Hello,
my tf700 doesn't finish the boot after I've installed CM.
Before flashing a new rom I've tried to make a system back-up from GooManager.
I don't know if the back-up is fully functional because in the "Breaking back-up in multiple archives" it has remained stuck at 100% (or complete progress bar) for like an hour.
After an hour or so I've interrupted the back-up process and entered the TWRP Recovery v2.5 (which I'm still able to access at the moment) and tried to flash a ROM downloaded by GooManager (cm-10.0.0-tf700t.zip). I've wiped the Dalvik cache and Cache in the process.
The flash seemed to be successful but the reboot doesn't finish, even though I've let it for two hours or so.
After that I've reentered the TWRP and tried a different rom cm-10.1-20130513-NIGHTLY-tf700t.zip, but with similar result, after installation it doesn't finish the boot.
I've reentered the TWRP and tried restoring the back-up. It did restored the system, passed the "configuring application" stage and gave the message "Finishing boot" and nothing afterwards, it just stuck in the process.
Right now I'm still able to enter TWRP, and navigate through the folders on the tablet, but I don't have a functional rom.
Can you please help me with some advices?
Thank you.
Which ROM did you have before, and which bootloader version?
_that said:
Which ROM did you have before, and which bootloader version?
Click to expand...
Click to collapse
Before that I had the stock ROM with the latest OTA firmware from Asus.
I don't know what was the initial version of the bootloader.
I've unlocked the device using Asus apk
I've pushed the TWRP on the tablet using the TF700T-ADB- Tool v3
I've granted super user rights from TWRP, I think using SuperUser application.
Ive installed from market GooManager and after that I've done what I've described in the previous message.
Thanks for your prompt answer.
Maybe CM is confused by existing data - did you wipe data (factory reset) as written in the CM instructions?
_that said:
Maybe CM is confused by existing data - did you wipe data (factory reset) as written in the CM instructions?
Click to expand...
Click to collapse
No, I didn't. I've just wiped the Dalvik cache and Cache.
If I do wipe data, I will still have user data, like downloaded ZIP ROMs or GAPPS zip?
I mean, at the moment I'm still able to try different ROMs and kind of operate the tablet. If I do wipe the data and is something wrong with the flash will I be able the try something else? Before I wipe existing data should I take other precautions?
Mihai_Preda said:
No, I didn't. I've just wiped the Dalvik cache and Cache.
If I do wipe data, I will still have user data, like downloaded ZIP ROMs or GAPPS zip?
I mean, at the moment I'm still able to try different ROMs and kind of operate the tablet. If I do wipe the data and is something wrong with the flash will I be able the try something else? Before I wipe existing data should I take other precautions?
Click to expand...
Click to collapse
From what I've read (but never tried myself), a "Factory Reset" is supposed to delete all your apps, app data and system-specific data, but not the contents of your internal emulated SD card. Your ROM and recovery are definitely not affected. But I'd wait until someone else can confirm.
It seems strange that the back-up isn't fully working either, it gets stuck after "Finishing boot".
I've noticed somtheing while flashing the two CM ROMs. On the instalation, of each of the two, it was a message that the MD5 is being checked, and after that that MD5 is missing and the check is being skipped. The instalation did continued and the message "Instalation succesful" was given.
But I don't know if it's alright not findind the MD5.
_that said:
From what I've read (but never tried myself), a "Factory Reset" is supposed to delete all your apps, app data and system-specific data, but not the contents of your internal emulated SD card. Your ROM and recovery are definitely not affected. But I'd wait until someone else can confirm.
Click to expand...
Click to collapse
I've checked on other sources and the wipe data seems to leave intact the user data.
But I'm still wondering at what state the tablet will be reseted since I've tried flashing to different ROMs and the back-up restore didn't work quite properly.
The last functioning ROM is still available from other means that restore back-up (which doesn't work) even though I've tried flashing new ROMs over it?
Mihai_Preda said:
On the instalation, of each of the two, it was a message that the MD5 is being checked, and after that that MD5 is missing and the check is being skipped. The instalation did continued and the message "Instalation succesful" was given.
Click to expand...
Click to collapse
The missing MD5 file is not a problem. If it says "installation successful", you can assume that it is.
Mihai_Preda said:
I've checked on other sources and the wipe data seems to leave intact the user data.
But I'm still wondering at what state the tablet will be reseted since I've tried flashing to different ROMs and the back-up restore didn't work quite properly.
The last functioning ROM is still available from other means that restore back-up (which doesn't work) even though I've tried flashing new ROMs over it?
Click to expand...
Click to collapse
Your backups not working is somewhat strange, but that's another area where I have very limited experience.
You said you were on the "latest OTA" stock ROM. Was that 10.4.4.25 (Android 4.1) or 10.6.1.14.4 (Android 4.2)? Also check the bootloader version - boot into the bootloader menu with holding volume-left, then read the tiny text near the top of the screen. It should contain the build number of your bootloader, which is identical to the build number of the stock ROM until you flash one of them separately.
_that said:
You said you were on the "latest OTA" stock ROM. Was that 10.4.4.25 (Android 4.1) or 10.6.1.14.4 (Android 4.2)? Also check the bootloader version - boot into the bootloader menu with holding volume-left, then read the tiny text near the top of the screen. It should contain the build number of your bootloader, which is identical to the build number of the stock ROM until you flash one of them separately.
Click to expand...
Click to collapse
It's Android 4.2.1: "Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.4-20130329" A03"
Right now the tablet is left with the attempted back-up recovery. Should I enter TWRP and do the wipe data or wipe data from the bootloader menu?
Or is something else that I should do first?
Ok, I did wipe the data, and even though it erased the user data too (media, docs, zip files etc) it restore the tablet to cyanogen mode not the original stock ROM. It finished the boot restore my gmail account. SuperUser is updated. And it seems the overall responsiveness is better.
Thank you for your time and advice!
Mihai_Preda said:
It's Android 4.2.1: "Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.4-20130329" A03"
Right now the tablet is left with the attempted back-up recovery. Should I enter TWRP and do the wipe data or wipe data from the bootloader menu?
Or is something else that I should do first?
Click to expand...
Click to collapse
OK, your bootloader is the latest one, and it works with Android 4.1 and 4.2 ROMs. There have been several reports of unrecoverable bricks after using "wipe data" from the bootloader menu with a broken or incompatible recovery - so even if your recovery works fine, I would not recommend to take any unnecessary risk.
If you have any important data on your device it would be a good idea to store a backup on an external microSD card, just in case you do wipe all data by accident or something unexpected happens.
_that said:
OK, your bootloader is the latest one, and it works with Android 4.1 and 4.2 ROMs. There have been several reports of unrecoverable bricks after using "wipe data" from the bootloader menu with a broken or incompatible recovery - so even if your recovery works fine, I would not recommend to take any unnecessary risk.
If you have any important data on your device it would be a good idea to store a backup on an external microSD card, just in case you do wipe all data by accident or something unexpected happens.
Click to expand...
Click to collapse
I'm surprised that after wipe data procedure it restored the system to a cyanogen mode not the original rom. I'm surprised by this because the last functional ROM was the stock one and because after flashing the last zip with CM ROM I've tried to restore the back-up ROM. Even though it didn't finish the boot, this back-up seemed to be installed over the previous CM ROMs. I'm not sure what happened, why I do have a CM ROM functioning, even though I did tried to install it I don't know why it managed to be installed.
If you have little more time and you know what happened here please let me know.
Thank you again!
Mihai_Preda said:
I'm surprised that after wipe data procedure it restored the system to a cyanogen mode not the original rom. I'm surprised by this because the last functional ROM was the stock one and because after flashing the last zip with CM ROM I've tried to restore the back-up ROM. Even though it didn't finish the boot, this back-up seemed to be installed over the previous CM ROMs. I'm not sure what happened, why I do have a CM ROM functioning, even though I did tried to install it I don't know why it managed to be installed.
Click to expand...
Click to collapse
The ROM and your data are completely separate. If you install a ROM and it says "install successful", the ROM is installed. "Wipe data" does not touch the ROM. However your data can prevent the ROM from starting up correctly. Apparently the restore fixed something in your data partition so that the last ROM that you installed can now boot.
_that said:
The ROM and your data are completely separate. If you install a ROM and it says "install successful", the ROM is installed. "Wipe data" does not touch the ROM. However your data can prevent the ROM from starting up correctly. Apparently the restore fixed something in your data partition so that the last ROM that you installed can now boot.
Click to expand...
Click to collapse
That means the TWRP didn't actually restore the ROM from back-up even if it did say the restore was successful...The last installed ROM was a CM one.
Thanks for the help!
Hey there!
I'm hoping that someone can help me out. My nephew who's a wanna-be geek was going to update my ROM (which didn't to be done really, but he wanted to show me what he was able to do). He went and downloaded the latest CM 11, rebooted and went into TWRP 2.7.0.1, did a factory reset, an advanced wipe, and did the Format Data. When he did that, it got stuck in a loop. Nothing happened. He tried to install the ROM he downloaded, and NOTHING! Long story short, by him doing the Format Data, he wiped out my partitions. TWRP, no matter what I try to do tells me it's unable to mount 'data' or 'media' etc. etc. Which is leading me to believe I have no partitions left. I've tried installing the latest update from Asus, and no dice. I've tried restoring backups that I have on my micro SD, and that's not working.
Can someone please help me and tell me how to fix this? Can I get my partitions back? I'm really hoping that I don't have to send this tablet off to Asus in Dallas, TX to have it repaired.
I'm using a loaner tablet from a rental store, hoping I can get my TF 300 fixed.
Any help is deeply and sincerely appreciated.
Omega
Sent from my SM-P600 using Tapatalk
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Duchman said:
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Click to expand...
Click to collapse
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Omega Recon said:
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
You could try flashing a newer recovery first, I think 2.7.1.0 is available for your device. Also try doing a hard reset by cold booting - here's a how-to: https://www.youtube.com/watch?v=oTU38Ewh8qo (wipe the cache afterwards)
If that doesn't help, reverting to stock is probably your best option. Try this: http://forum.xda-developers.com/showthread.php?t=1757077 (be sure to grab the correct firmware and back up your files)
Have you tried installing any other custom ROM? Does it give you the same error when you try to restore your backup?
Here's what I've come across so far. I did the reset, and that did nothing.
Tried to flash the stock version, after a few seconds, TWRP popped up with FAILED.
I've tried flashing Omni ROM. It will flash, load up, and gets stuck at the boot screen or boot animation. This happens with just about every ROM I try to flash.
Been looking for TWRP 2.7.1.0. I'm not seeing it listed on TWRPs site. Where can I get a copy? Thanks!
Sent from my SM-P600 using Tapatalk
Here you go: http://forum.xda-developers.com/showthread.php?t=2772093
Also do try flashing another recovery, PhilZ for instance: http://forum.xda-developers.com/showthread.php?t=2597860
Did you try wiping all of the partitions again?
So I was using Calkulin's stock 33R with AK kernel, which has been running fine. I deciced that I should try PA, so i did my regular thing of making a nandroid backup, wiping /data, /system and /cache. Flashed PA and the relevant Gapps, and got stuck on PA bootscreen. So I tried it again, and upon closer inspection, in, the flashing of Gapps failed because it was unable to find build.prop.
So I tried it all over again just with PA, no Gapps, no anything else. Same result, just the PA boot animation staring at me for over 20 minutes.
I then tried flashing Clakulin's stock again, and no luck, still stuck on OPO logo screen. I thought perhaps my partitions were messed up, so I wiped everything and flashed stock 33R from CM. Well, at least that booted and my EFS data was intact. I then tried reverting to Calkulin's stock by sideloading, and it never went past the boot screen.
Bottomline: I cannot use any ROM apart from stock 33R. Installing a kernel on top bootloops, installing root bootloops, installling a ROM bootloops, almost anything I flash bootloops. This is driving me nuts.
I am using the latest Philz recovery and my BL is unlocked. I am also a very seasoned flasher and I know what I am I am doing. Yet, this issue is boggling the crap outta me.. I know the solution is probably simple, yet I'm overseeing it.
PLS DON'T KILL ME FOR NOT PROVIDING A LOGCAT. I'll provide anything requested by those helping.
EDIT 1: When I say flash stock 33R, I am referring to the factory image provided by CM on their site. Also, remmeber the nandroid backup I made? That failed to restore. Yea, it failed hard on me.
EDIT 2: I remmeber reading in another device forum where his recovery was mounting the wrong partition when flashing, which makes sense since Philz's recovery produces an error where gapps can't find build.prob. I checked the recovery settings and the only mount I can change is SD from /media/0 to /media/
EDIT 3: I want to shoot the phone, and then myself.
Perhaps try using TWRP, just to rule it out?
EddyOS said:
Perhaps try using TWRP, just to rule it out?
Click to expand...
Click to collapse
Tried TWRP, no error on flashing the Gapps, but still stuck on boot animation.
If you flash the stock factory image does that work? I know you say you can 'use stock' but you don't say whether that was your backup or the factory image
EddyOS said:
If you flash the stock factory image does that work? I know you say you can 'use stock' but you don't say whether that was your backup or the factory image
Click to expand...
Click to collapse
I meant the stock factory image. My nan droid failed to restore.
I'm stumped cause if the factory image works so should everything else. Bizarre!
Hope you get it fixed soon, bud!
One last thought - I assume the md5s matched on the files you tried to flash, correct?
EddyOS said:
I'm stumped cause if the factory image works so should everything else. Bizarre!
Hope you get it fixed soon, bud!
One last thought - I assume the md5s matched on the files you tried to flash, correct?
Click to expand...
Click to collapse
All md5s matched with the files. It IS really bizzare indeed. I searched about this problem for several hours, even on other devices. But no luck!
Try an older factory image and let it boot and do all the ota updates and try then that's what i did
gavin-phelan said:
Try an older factory image and let it boot and do all the ota updates and try then that's what i did
Click to expand...
Click to collapse
Tried that too. Started off from 25, moved to 30 and still no luck.
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
I just unlocked my boootloader today after waiting the 14 days. First thing I did was install twrp recovery, had no problem there. Then I downloaded unofficial lineage os 14 rom, and the newest open gapps.
I was able to fastboot boot into twrp recovery, I then wiped dalvik, system, data, and cache. then proceeded to install lineage os rom, no problem, when I tried to install gapps, it just hung on detecting device and rom. which I had to reboot. then it came up to black screen with blue led. again I rebooted into twrp recovery, wiped again, and this time just installed lineage os rom, and reboot,same thing black screen with blue led. did I miss a step somewhere?
If you were on stock mm or below s244 stock then it's normal to see this..
Sent from my Lenovo P2 using Tapatalk
FireLord said:
If you were on stock mm or below s244 stock then it's normal to see this..
Click to expand...
Click to collapse
+1
Install s244 firmware and then install los.
In trying to fix my own problem I may have screwed it up more. I changed the file system of the Systema nd Data partitions. I changed it to EXT4, however that did not help. I would like to change them back to whatever they were before, but I dont know what they were before, can anyone help me?
actionxp said:
In trying to fix my own problem I may have screwed it up more. I changed the file system of the Systema nd Data partitions. I changed it to EXT4, however that did not help. I would like to change them back to whatever they were before, but I dont know what they were before, can anyone help me?
Click to expand...
Click to collapse
Stock is f2fs, if I'm not wrong
I have this same issue but it solved , i change my data partition to ext4 and also changed another partition to ext4 i didnot remember which partition is that, i think it is system partition (not sure)
actionxp said:
In trying to fix my own problem I may have screwed it up more. I changed the file system of the Systema nd Data partitions. I changed it to EXT4, however that did not help. I would like to change them back to whatever they were before, but I dont know what they were before, can anyone help me?
Click to expand...
Click to collapse
Don't messup with system partition plax..
I had the same issue. Try an other Gapps pack. I picked a smaler one and it worked.
Yes it was that easy
So i installed the S244 Firmware, installed twrp and even got stock rom+magisk root to work. I passed safetynet test. But i can't flash custom roms+gapps. It freezes in twrp.
I already tried alls opengapps versions, from pico until micro. None of them worked. My system partition is ext4, same as data.
My twrp version is 3.1.1-1