Unfortunately, I can't post in developer as I'm a new account. I've been a lurker for a long time, but never needed to login!
Just installed Baked Black Beans 9 Rev6, and I'm in a bit of a circle here!
Tablet Z (SGP312) is stuck in Baked loading screen
-Fastboot fails - I get a flashing red light and the baked logo same as a normal load. Can't flash a new BIOS into the unit via fastboot or adp on pc.
-No Recovery mode - it appears as though the BBB9 load is hanging/stalling PRIOR to the recovery (no status light at all)
HELP!
Related
Help! I just got CM 10.21 emmc running on my 8 GB NT and was becoming familiar with the system. I installed AdAway and after setting it up allowed it to reboot. Mistake!
This is the first time I've rebooted or turned off since the ROM flashing. I get the "N" screen, then an unnerving flash, followed by the Cyanoboot universal bootloader screen and it says "Loading (EMMC)...". Then all goes black :crying:
There is still backlighting and holding the power button will eventually extinguish it. Plugging the tablet into the charger (or the PC) has no effect (off or on).
It did the flashing according to this thread and everything went as described. The tablet has behaved flawlessly until this. I could theoretically recover to stock and start over again but if there is a way to fix this, I'd rather.
EDIT: Update. I tried booting with the CWM SD card that holds the recovery files as well as the files used to flash the CM 10.21 ROM. I get a red bar message that says "booti: bad boot image magic (in memory)". Underthat is "(SDC) LOADING BOOT...." and it's just stuck on that screen.
EDIT2: Solved itself eventually after a number of attempts. Really freaky behavior.
I have followed a few of the tutorials with some success but did a mis-step somewhere along the way pursuing S-OFF. While not a total noob with modding (Consoles mainly) this is the first time I am truly lost in the process.
Excuse me if I use a wrong term here and there, I probably need to have a sleep as I have been working on this (from start of initial Mod) for about 17 hours straight (Overnight).
So I have a HTC One M7 UL that I have unlocked and has TAMPERED showing on the Boot screen. :good:
When I power it up it freezes at the white HTC powered by ANDROID screen.
I can get to the Boot menu, and I can select Recovery but it shows the screen for loading the which ever tool I have managed to flash (so yes I have the ability to flash and can swap between Clockwork and TWRP versions with flashing)
I can't list devices or start a shell session, as it thinks that USB debugging isn't turned on. Up until I caused the FUBAR USB connection was working fine.
Holding Power Button doesn't shutdown, just reboots, but can achieve shutdown through boot menu.
How do I get a working phone again?
Ok I soleved it myself. Found a boot.img flashed it over and the custom recoveries work again. Now onto getting S-OFF so I can get Google Play Edition.
A few months ago, I moved from stock Asus ROM to CyanogenMod 13 ( Phone rooted, bootloader unlocked and TWRP installed), although recently I wanted to move back to original ZenUI due to battery drain and a couple of minute bugs, I decided to flash the ROM through TWRP (biggest mistake of my life) this is the stuff I did :
1. Downloaded Stock ROM for my Zenfone 2 Z008
2. Copied it to SD Card along with CM13 and GApps Super package as backup
3. Went into recovery mode (TWRP) to flash the ROM
4. Erased everything except SD Card
5. Attempted to install stock ROM, after a few minutes it failed [ it was stuck on something "mounting...."] (I know I'm a noob)
6. Thanks to the CM backup I flashed it along with the GApps
7. Rebooted phone
AND BAM!
No booting screen , no booting animation just an illuminated black screen, after a while it showed the welcome screen of CM 13 asking me to enter details - Language , Google account blah blah blah...
Till date whenever I switch on my phone there's no booting animation (not even the ASUS logo which comes before the booting animation!) And somehow after a while of black screen my phone displays my lockscreen and I am able to use it.... Now the best part, I can't access my bootloader! Everytime I try to open it (be it from pressing the buttons to using an app to easily access it) bootloader won't open. Upon using the Volume down + Power button combination the phone vibrates a little and nothing happens while it's supposed to give two long vibrations , though it does give the long vibrations upon normally booting the phone or while putting it for charging while it's switched off (Yes the charging animation is there)...
So yeah, I need your help guys...
Afternoon
I have a Lenovo 7" tablet which is sticking on boot...to describe:
tablet off, charge screen working fine (green battery)
can get into menu to select fastboot mode or recovery
fastboot works, at least screen appears!
recovery shows dead android/no command screen - how to access recovery?
booting up, get inital orange logo then a 'bing' and start of boot but then freezes on the second logo
tablet not visible on PC, even in fastboot mode (have installed drivers)
I'm looking to get this going but am a bit stumped. I tried reinstalling firmware but can't get SPF Tools to work with any available scatter files; I would like to install TWRP (I found a potential image file on XDA) but can't do this until the PC recognises it....and I'm going round in circles now....any suggestions gratefully received. :good:
Update
OK, post was maybe a bit premature - I've kinda fixed my issues.
Managed to get into recovery after watching many videos (most of which were wrong, but hey-ho, got me on the right path!). At dead android screen, press and hold in power + vol up + vol down together (there is a bit of knack, turn it on its side with buttons facing up seems to be easiest) - this fires up the recovery screen (android standard recovery).
I managed to get over my bootloop issue by performing a data wipe/factory reset and cache wipe, then restarted fine.
As this was a secondhand tablet (my usual purchases - good condition bootloops!) - once it booted up I got into the set-up screens only to discover a Google lock issue. I ran the FRP unlock from here: https://androidfilehost.com/?fid=11050483647474832839 using the instructions from here: http://forum.gsmhosting.com/vbb/f958/lenovo-tab-4-7-essential-tb4-7304f-frp-remove-2322527/ (Voltrans second post, not the original one which has a 404 error on the download site). This removed the FRP lock straight off and now I have a functioning tablet.
I'm probably going to try getting custom recovery on so will see how that goes - I'll post back
and...that's all folks....
OK, despite finding a TWRP recovery online https://twrpbuilder.github.io/downloads/twrp/#441 and downloading it, can I get the fastboot unlocked? no.
Apparently Lenovo locked them all up and threw away the key, so nothing more can be done here.
I tried various iterations of fastboot oem unlock and fastboot flashing unlock, and nothing works, just get an error - and yes, I did put developer options on, OEM unlocking ticked and USB debugging active.... :silly:
So, unless someone can point me in a direction on how to unlock it - I've reached the end of the road with this one
Hello
I have UmiDigi F1 Play stuck in a boot loop.
So, the phone was working fine on "UMIDIGI F1 Play V1.0_20190903 ROM - SPFT + OTA release" updated via OTA. One day after a normal restart the phone went into a boot loop (UmiDgi logo, <thinking>, black screen (displayed not turned off), <thinking>, UmiDigi logo, and so on).
So, these are the steps I took so far with no luck:
1. Managed to get into recovery (pressing repeatedly Vol-Up while UmiDigi logo comes on), and did factory settings restart, still boot loop. "Mount /system" still boot loop. "Wipe cache", still boot loop. Also at times when I got into recovery browsing through the options was super slow - one pres vol-up or vol-down and it took three seconds to move to the next option in the menu.
2. Reflashed in Download only mode the ROM "UMIDIGI F1 Play V1.0_20190903 ROM - SPFT + OTA release" via SP Tools, still boot loop.
3. Downgraded using Flash firmware mode to the oldest available ROM - "UMIDIGI F1 Play V1.0_20190409 ROM - SPFT release", still boot loop.
4. Formatted everything including bootloader, flashed again the newest "UMIDIGI F1 Play V1.0_20190903 ROM - SPFT + OTA release", restored IMEIs, still boot loop.
4. Occasionally the phone loaded the system, but after system restart there is still a boot loop. Moreover, in the top right corner there are two lines saying "TEE: <Chinese symbols> Google: <Chinese symbols>" visible at all times in Android, despite correct IMEIs being present.
5. Flashed again the newest "UMIDIGI F1 Play V1.0_20190903 ROM - SPFT + OTA release" but this time I've read somewhere to press and hold both vol-up and vol-down before connecting the phone to the computer to supposedly enter safe mode. It only resulted in displaying single green pixel in the top-left corner at all times in boot loop.
6. I've unlocked the bootloader via Developer options in Android when it miraculously loaded. Tried to flash TWRP via ADB - the phone displays that bootloader is locked. Tried flashing TWRP according to the instructions on the UmiDigi forum via SP Tools and there is a text under UmiDigi boot logo saying "Red state <you're using custom recovery use OEM recovery this will not start>". The text is displayed for a very short period of time and the phones goes again into a boot loop.
So to sup up:
- the phone has the newest stock ROM "UMIDIGI F1 Play V1.0_20190903 ROM - SPFT + OTA release"
- is stuck in boot loop (UmiDigi logo, <thinking>, black screen (displayed not turned off), <thinking>, UmiDigi logo, and so on)
- in the boot loop there is single green pixel in the top left corner at all times
- when the system occasionally loads there are two lines visible at all times saying "TEE: <Chinese symbols> Google: <Chinese symbols>"
How do I fix that guys? Any ideas?
SOLVED
So, I solved my bootloop issue.
The reason for bootloop was faulty fingerprint scanner. I've disassembled the phone, disconnected the FP scanner and phone boots as it should.
However, don't throw away FP scanner if you won't replace it. You will need it if you will want flash in the future anything via SP Tools - flashing without will result in bootloop.
so how did you get rid of the chinese red letters??