Hi guys,
After searching for a few days and doing stuff myself (perhaps not everything for the best), I finally get it over with and ask for advice.
I've got a GT-N8010, since long been running an unofficial CM11 build (since one of these CM11 builds, the device was known as a GT-N8013).
Last week I started looking at the unofficial CM12.0 and CM12.1 builds, those looked promising.
After some info, I flashed to the CM12.1 build. A few minutes later, Android 5.1 in all it glory... everything running fine. Saturday evening I noticed I didn't get root.
Without thinking straight, the next morning I started flashing superuser but as you might imaging, that totally f'ed the system.
Now logically, one could just reflash CM12.1 and be done with it .. somehow I skipped all logic and started tinkering in recovery (TWRP).
After some doing, I managed to even F-up TWRP, it wouldn't boot anymore. The TeamWin logo was visible, screen flashed, logo and back.
No worries, there's still the download mode .. yeah about that ... already in panic mode .. doing more harm than good.
So .. Now I'm at this curious state.
I've managed to get it booting to a stock ROM. TWRP is also running.
The weird stuff I'm encountering now:
The device is semi recognized as a GT-N8000, if it was just that, I really don't care.
I said semi, when I want to flash another ROM (even specifically the CM12.1 for GT-N8000) it always states (in ADB Sideload in TWRP) that the package is not for this device.
There's a whole lot of devices listed, then it states "this device is ." , as in blanco device?
Anyone got an idea how to fix it so I can enjoy the Android 5.1 build again? (and seriously, remove the stock rom would be the first priority)
Thanks.
Related
I have a new tf300t with Android 4.1.1 on it and I have followed an older guide to unlock the device and it said to put clockworkmod on it and the Cyanogenmod forums indicate a problem with that, so I went TWRP instead. The twrp site said to pick the right version (-jb) and I did that.
I put 2.6.latest of twrp on and did a backup. Everything is going great. I rooted the device with SuperSU, Copied over CM 10.2.nightly and the right gapps version and it flashed fine. I booted in and I let it go for awhile and it just bootlooped. I went back into twrp and reflashed to ensure that wasn't an issue (same problem) and restored and I'm back to the beginning. I decided to try the 10.1 version on Cyanogen's site and had the same issue. I'm thinking it's the bootloader version doesn't match -- needs to be 4.2, but I want to be careful not to brick the device since a lot of people have done that.
Any guidance or pointing me at a thread would be appreciated. I have a feeling that letting the OTA update take place on the device kind of ropes me into a corner I might not want to be in. I'd really like to be on the latest Android OS *assuming* most of the tf300t features work. I can handle some odd things not working quite right.
Thanks,
Rich
Step1
It appears that my semi-direct path is to get to the newest [MINUS 1] version of 4.2.1 from Asus.
TF300T-US_epad-10_6_1_27_1-UpdateLauncher.zip
Many newer ROMS require this boot loader, and many people say to stick with the twrp 2.5.0.0 because 2.6.x.x is buggy. I can confirm that 2.6.x.x (latest), the mount feature does appear to be broken.
My only concern now is timing. Upgrade to 2.5.0.0 first, or upgrade using fastboot to the new Asus rom. It might not matter and I might need to put TRWP back on after the flash anyhow.
Also, I did root my current OS before doing this update, so it will be interesting to see if that remains intact.
Rich
Step3
I used fastboot to update and I thought I could apply the TWRP 2.5.0.0 update right after it, but it wouldn't take it. I was a little worried that I borked it. It booted and went into the OS and updated a bunch of things. I noticed my SuperSU was no longer root even though it was going to try and survive the update.
Also: I switched to the 4.2 Launcher... not sure I want my tablet to run just like my phone. I might switch back.
I'm still going to try and get to a CM 10.2 rom, it might not be an official rom though.
Rich
Step 4
I decided to see where things were at with a fully tweaked 4.2.1 rom before the 4.3 rom and picked
[ROM]★●[TF300T/G/L/201/301][CROMi-X 5.0.2][ODEX/DEODEX 10.6.1.27.1][SEP 8]●★
This looks very well done/well polished and has lots of people testing it. Will update as I head to 4.3.
Please pardon me for any faux pas as I am new here.
Mods please refer me to the appropriate thread and close this one, in case this one is a duplicate.
It seems my Moto G 1 Gen XT1033 is hardbricked. I had been running a CM 12 for falcon - nightly release since May 2015 and had had no problems so far. I had also upgraded my recovery to CWM Touch.
Two weeks ago, my phone got stuck in a boot loop (I now realise that that is called a softbrick), I managed to boot into recovery and updated my OS with the latest nightly release of CM 12 for my phone. I also tried to upgrade the recovery version with the same as that of the OS version but I don't think that it got upgraded. (I'm not sure what it said).
Anyway my phone was working fine for an hour or so until CM gave some errors on opening the themes configuration, so I thought rebooting my phone would solve the problem.
My phone never booted after that. It didn't even turn on or boot into the bootloader/recovery etc. I checked the battery etc. and it was fine. There was no issue with the hardware.
I then connected my phone to my laptop and it recognised it as qhsusb_bulk. I have spent a lot of time searching and trying various methods like:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
http://forum.xda-developers.com/moto-g/orig-development/bootloader-tool-motoflasher-t2959076
Using the MotoTool All In One etc.
I cant seem to figure out the problem. I don't even know what my bootloader version was etc.
Is there a problem with my bootloader or recovery? I can't seem to understand.
Can someone please help me with this?
Thanks
Oh man that's unexpected. I never think CM could cause this. I hope you can get it fixed.
Bumping the topic
motolollipop said:
Oh man that's unexpected. I never think CM could cause this. I hope you can get it fixed.
Bumping the topic
Click to expand...
Click to collapse
Thanks man. But no help so far
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Tass99 said:
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Click to expand...
Click to collapse
No bro. I've bough a spare phone to survive on till I get a solution for this.
But nothing has worked so far.
CoolCrusader said:
No bro. I've bough a spare phone to survive on till I get a solution for this.
But nothing has worked so far.
Click to expand...
Click to collapse
That happened to me too, I think even the same image! It was a long time ago and I have now switched to a Oneplus One after using a Moto E which actually isn't that bad - I got it new super cheap. For me, Cyanogen restarted to update and after a LONG period of time stopped doing anything (I have upgraded before). I couldn't mount anything in CWM and I lost all data irrecoverably. The partition table got all messed up, and I had to flash a dual sim image as it was the only one that loaded - done through fastboot. I then flashed the original kitkat image and then massively messed up and updated, making my phone qhs_bulk.
Basically everyone who has had lollipop on their devices and have this are waiting for files to be leaked from Motorola so they can make their phones work. Not much is happening currently, you might as well get a new budget phone - some of the new ones are much better than the Moto G 1st gen! Or you could do what some people are doing which is ordering broken Moto Gs off eBay and replacing the board. Good luck!
---------- Post added at 01:49 AM ---------- Previous post was at 01:42 AM ----------
Tass99 said:
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Click to expand...
Click to collapse
You may want to go the fastboot method to flash a stock lollipop image and CWM recovery - if you don't have a backup, you may want to try just flashing something like TWRP to see if you can get some files off your device, then completely flash over it.
Besides my comments in the title, the only thing my K1 can do right now is go into the bootloader and nothing else.
The Story:
I was running Blisspop 4.0.3 (Lollipop 5.1.1) then flashed to Blisspop 6.0 (MM 6.0). After that, it wouldn't boot into the OS. I did a complete wipe of everything and tried to flash Blisspop 6.0 again, same outcome. I heard I needed to get my hands on TWRP 3.0.0.0 to get MM roms up and running. My dumb ass flashed it and now, I don't have a recovery either now because it gets stuck on the first slpash screen. I went digging around the forums here and I felt like I read something about doing a bootloader update. If that's true well then I done messed up now. At this moment in time, I am only able to launch the bootloader but for the life of me, I can't get ADB to detect it connected to my computer to fix these issues. So as of right now, it's a $200 brick. If anyone can point me to some awesome tools to hack my way around this conundrum, I'd love you forever. Thanks in advance for listening to my problems.
Hey Folks,
got some messy Prob's with my old nVidia Shield LTE Tablet.
The Facts:
-KillSwitch not Triggered and it was succesfully Rooted in November 2015, TEGRA-OTA was also Removed (nomoreota)
-worked for Months (beneath one year), only Super-SU penetrated me periodely that it needs to be Updated, but it couldnt be done, it said "not enough Space" after trying to install a newer Version. :silly:
-past Month (January 2017) i decided to do a Factory-Reset, because Girlfriend should get the Shield, thats where the Problem started:
After clicking Factory-Reset, it began to work. After 4 Hours and nothing happening, i decided to Power it Off and start fresh with Installing a clean Stock-ROM and remove the TEGRA-OTA as i done a year before.
But from now on things get messy and to complicated for me.
In the Past i rooted and flashed it with "Shield-RAM", found here on xda.
But this Time it didnt ended with a working Shielt-Tablet. It stucks alwas in a Bootloop, in Recoverymode also as in normally booting the flashed OS.
Confused an disturbed by this, i tried different Recoverys (TWRP 2.8 and 3.0, also a CWM), all with the same Effect: Bootloop
Now i only can acces the Bootmenue which says Bootloader Unlocked.
I dont now what to do from here on and would be very happy and glad, if someone can help me figuring out whats going wrong.
If further Details are needed i will do my best to provide things i forgot here to mention.
With kind regards - ToxicFighter1
Ps.: excusy my bad spelling, bit rusty in flawless english typing:good:
Hi !
There is this thread where you can try to get it back to stock https://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541
This nice index may help as well
Good luck !
Thanks, but that's not the problem. If I boot into Fastboot / Bootloader, it's totally fine. In fact, I can plug the tablet up to my PC when it's in any state and doesn't experience the issue. It only occurs when I have it plugged into AC. SO far, I've tried 3-4 different cables and power supplies for 2.4A, 2.1A, and 1.2A - all adapters which worked 100% prior to updating.
Suggestions?
OK - Finally fixed it...
I replaced everything as shown above, but ran into the issue again as soon as FlashFire installed the OTA. So, I tried a different way to upgrade and no longer have the issue. Below is what I did...
- Installed 4.4.0 via ADB/fastboot wirhOEM recovery
- Completed initial setup and upgraded to 5.0 via built in system update
- Rebooted
- Booted to bootloader and flashed TWRP recovery
- Booted to TWRP
- Installed SuperSU via sideload
I would have started out applying 5.0 via adb/fastboot, but have yet to see a full image available yet. Used same TWRP and SuperSU as originally used. Just eliminated GlashFire from process. Once I rebooted and everything loaded, plugged into 2.4a power, and it worked without going into boot loop.
Hope this may help someone else - Thanks
Hey Folks,
thx for the few answers, i'll try these Tips out the upcomig Days.
Lot'a Stuff to do atm, bit Busy.
With kind regards - Toxic
xanthrax said:
Hi !
There is this thread where you can try to get it back to stock https://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541
This nice index may help as well
Good luck !
Click to expand...
Click to collapse
Hey there, and personally Thx for the provided Link.
As announced i did try it, but with no Success.
I'll or explicit the Tablet gets Stuck at Step 17, the Bootsreen doesn't disapear.
Dont know whats Wrong, cause i did all as menitioned in the Post, every ADB/Fastbootstep with Succes-Message, and because Bootloader was already Unlocked, i took the Rooted Image.
But now, im still on Bootscreen, sick
With kind regards!
Tried lineage-14.1-20170305-UNOFFICIAL-n8013.zip on a Galaxy Note 10.1 GT-N8010 (16GB), but after reboot, i am stuck in a never ending "boot logo" (?) (blue circle repeatedly shifting from right to left on a blue bow, nothing else), tried it twice, waited twice for more than 15mins, nothing changed (nevertheless, I could successfully install cm-13.0-20160831-UNOFFICIAL-n8013.zip).
Has anybody sucessfully installed 14.1 on a GT-N8010 ?
Further info: I have an additional 64GB-SD-card where I stored the aforementioned lineage file as well as open_gapps-arm-7.1-nano-20170418.zip and open_gapps-arm-7.1-stock-20170418.zip.
Tried all installations (also cm-13) using twrp-2.8.6.0-gt-n8010.
Any comments appreciated, even more so if they help getting 14.1 installed.
Regards
aqua14
2017-04-19 10:30 (MESZ)
Additional observation while again trying to install lineage-14.1-20170305-UNOFFICIAL-n8013.zip:
* Meanwhile I found that lirokoa recomended the TWRP version mentioned in the CM13 thread, i.e. twrp-2.8.7.0-gt-n8013 (instead of 2.8.6.0 in my first try) and managed to install it on my Galaxy GT-N8010, but after all, this made no difference.
* However, while carefully watching the flash log I found that the "target" was logged to be "samsung/p4noterfxx/p4noterf: 4.4.2/....", and not "samsung/p4notewifi...." as I rather would expect for a GT-N8010.
Hence my question: can it be that (a) either during the paketing of lineage-14.1-20170305-UNOFFICIAL-n8013 something went wrong, or that (b) my tablet pretends to be a different one (namely GT-N8000)? I suspect this confusion could be the reason of the aforementioned boot trouble.
At least I am sure of this fact: I haven't got a tablet with phone function, its the version only having the wifi function, and in the system info provided by JellyBean as well as KitKat I could read its the GT-N8010.
Any constructive hints or suggestions appreciated
Regards
aqua14
Additional observation:
* Both lineage-14.1-20170305-UNOFFICIAL-n8013.zip and lineage-14.1-20170116-UNOFFICIAL-n8013.zip don't work on my GT-N8010 (reboot after flashing leads to a boot loop) , whereas cm-14.1-20161208-UNOFFICIAL-n8013.zip did work (not everything tested yet, but wifi, installing apps (another keyboard, file manager, ...) worked ok.
2017-04-20
Eventually ...
I guessed just from the beginning, that the right path might again be hidden in all the tidbits given in the discussion around the lineage 14.1 thread (hxxps://forum.xda-developers.com/galaxy-note-10-1/development/rom-nougat-t3505239)
... and indeed! It took me a while to crawl through all comments, questions, answers, and unfortunately also complaints, the latter in some parts being expressed even in close-to-nasty manners. Being a developer as well (DB area) I as well appreciate constructive criticism and prefer it to demotivating complaint. However, some of the participants obviously never have learnt making an effort to keep the difference between both, maybe they are even unlucky enough not to perceive hours and hours of voluntary work of their contemporaries as a gift. Hey guys! Behave!
Whatsoever. I finally made the way through the texts and even managed to install the latest version (lineage-14.1-20170305-UNOFFICIAL-n8013.zip) and ... beneath my sincere thanks going to lirokoa (taking a bow 4 u), I'd like to greet and thank all the testers *and* contributors of helpful hints (regarding the installation of the ROM itself as well a manifold of aspects to special apps), also including especially those who took their time to precisely & factually describe which procedure did fail (!), which -in sum- made my day start successfully now!
For all those still struggling: keep trying!
After all this reading I restarted a new try and had my breakthough ~after having read the following comments in the aforementioned thread: #352/p.36, #364+#365/p.37 and some others of similar content, hence thanks also to alessandro_xda, hektor2hektor2, CDiazF04, but also all the others who keep the discussion vivid and interesting, and a special smile to miz_pimp for having increased the level of friendliness throughout the course .
And yes, I agree that many contributors are right in suggesting to include the one or other hint to the post #2 of liroka.
I guess it's presumably just lack of time on his side that this has not yet happened. On the other hand... :-> if I could walk through all the interesing discussion in one evening and draw my conclusions in order to get a free ride to another "new life" of my ol' N8010, ... I am quite positive that others can do so as well.
Continuously following the discussion...
aqua14
Thanks guys!
Just had the same problem. I just needed to upgrade twrp and try again. I really appreciate this site! Now my old tablet is doing better than my husband's new one.
Finally loaded Lineage 14.1
I have just updated my GT-N8010 with lineage-14.1-20170810-UNOFFICIAL-n8013.zip + open_gapps-arm-7.1-mini-20181010.zip & used the latest TWERP release 3.0.2 to do this.
I initially tried loading these two as above, the first issue was that having loaded them the tablet would get stuck with a battery symbol and would not boot. The way I found around this was to boot the tablet into Odin mode but choose Reboot Phone rather than going into Odin itself. This then enabled Lineage to boot but it then got stuck in a loop, the lineage logo would go through its line with a moving O, then have three O's and start again.
Eventually I found that I could get cm-13.0-20160831-UNOFFICIAL-n8013.zip to load with open_gapps-arm-7.1-mini-20181010.zip and this worked well. I then did a dirty load (No Wiping) of lineage-14.1-20170810-UNOFFICIAL-n8013.zip and this is now working without problems.
Hope this helps and best of luck!!
macgd016 said:
Finally loaded Lineage 14.1
I have just updated my GT-N8010 with lineage-14.1-20170810-UNOFFICIAL-n8013.zip + open_gapps-arm-7.1-mini-20181010.zip & used the latest TWERP release 3.0.2 to do this.
I initially tried loading these two as above, the first issue was that having loaded them the tablet would get stuck with a battery symbol and would not boot. The way I found around this was to boot the tablet into Odin mode but choose Reboot Phone rather than going into Odin itself. This then enabled Lineage to boot but it then got stuck in a loop, the lineage logo would go through its line with a moving O, then have three O's and start again.
Eventually I found that I could get cm-13.0-20160831-UNOFFICIAL-n8013.zip to load with open_gapps-arm-7.1-mini-20181010.zip and this worked well. I then did a dirty load (No Wiping) of lineage-14.1-20170810-UNOFFICIAL-n8013.zip and this is now working without problems.
Hope this helps and best of luck!!
Click to expand...
Click to collapse
Have you tried out my LineageOS 14.1 ROM? https://androidfilehost.com/?fid=1322778262904016892
I'm sorry to say that I have not as I was not aware of your rom till now so thanks for for your post and I have downloaded it just in case I find issues with 14.1-20170810. Out of interest how does it differ from 14.1-20170810
macgd016 said:
I'm sorry to say that I have not as I was not aware of your rom till now so thanks for for your post and I have downloaded it just in case I find issues with 14.1-20170810. Out of interest how does it differ from 14.1-20170810
Click to expand...
Click to collapse
Mine is more up-to-date. But I will be making a update for that ROM later this week.
Here is my thread for the ROM: https://forum.xda-developers.com/galaxy-note-10-1/development/rom-lineageos-14-1-t3848514
Oreo rom for Samsung galaxy note 10.1 gt n8000
Pls any Oreo rom for gt n8000 my nougat rom can't play videos since i rooted it, after unrooting it still can't play any video. Pls is there any fix.
Flash stock rom via Odin.
JJEgan said:
Flash stock rom via Odin.
Click to expand...
Click to collapse
Will flashing the phone with lineage 14.1 again help? Cus I can't go back using stock rom
Back to stock then flash custom rom.
Problems fixes use SEARCH.
Rom is in testing so its up to you to flash with potential problems or not .
I have the same problem. Note 10.1 N8010 and it is stuck on the logo " blue circle repeatedly shifting from right to left on a blue bow".
I cannot locate the file TWRP for the note 10.1 N8010.
The suggestions were to update Twrp but the file I have found online is (
twrp-3.4.0-0-lt03wifiue.img.tar7.5M2020-06-23 21:11:34 EDT
This file is loaded using odin and it is successful but the Twrp doesn't work anymore. Therefore, I had to go back and load the file (twrp-2.8.6.0-gt-n8010.tar).
Can someone please help me with this issue.
TWRP site is twrp.me
Có ai up rom android 7.1.2 hoặc 9.1 cho galaxy GT-N8010, qua TeamViewer không? cảm ơn.
[email protected]
Translated by GT:
Has anyone uploaded rom android 7.1.2 or 9.1 for galaxy GT-N8010, via TeamViewer? thank.
[email protected]
See your other post