Hello all !
(First, sorry if I don't make myself clear enough, I'm french..)
Today I updated the Paranoid Android rom from the OTAParanoidandroid app, and when it said it was rebooting, the screen went off in a weird way.
I rebooted it and it was stuck on the boot animation (with the colourful spheres) for like an hour. I gave up, pressed the power + Volume up button, and went into recovery.
I tried updating it from here, but I've got the same problem, the boot animation takes ages !
So I cancelled it again, and I tried to wipe the cache and the dalvik's one.
When I rebooted it, it said it was updating android apps, but when it came to '"starting apps.." it remained stuck for 10mn..
After That, I managed to have it working with my PC, I reflashed the G apps and the Rom.
But Maps "stopped working" everytime
I tried a previous version of gapps, deleting the cache... Still nothing !
Salut !
Il y a un problème avec la beta 2 de paranoid, le module GPS semble ne pas être inclus... En attendant que ça soit corrigé, je pense qu'il vaut mieux retourner sur la beta1 :/
nhibel said:
Salut !
Il y a un problème avec la beta 2 de paranoid, le module GPS semble ne pas être inclus... En attendant que ça soit corrigé, je pense qu'il vaut mieux retourner sur la beta1 :/
Click to expand...
Click to collapse
Hello !
Finalement j'ai fait un wipe complet et réinstallé la beta 2 et les gapps 4.4.4... Mais le gps fonctionne très bien pour moi
Known issue in Beta 2
http://forum.xda-developers.com/showpost.php?p=55707753&postcount=3691
In Beta 1 GPS is working but there are Problems with the camera (taking 10 seconds to Start, also for Flashlight)
Targunitoth said:
Known issue in Beta 2
http://forum.xda-developers.com/showpost.php?p=55707753&postcount=3691
In Beta 1 GPS is working but there are Problems with the camera (taking 10 seconds to Start, also for Flashlight)
Click to expand...
Click to collapse
Hey, thanks for your answer.
IDK why, but the GPS is working on my BETA2.. Is this bad ?
of course it is good if it is working
Are you sure you are on Beta 2 and not getting your possition over WLAN?
Did you do a clean install of Beta 2 or first with Beta 1 and then Update?
Is your Problem
But Maps "stopped working" everytime
Click to expand...
Click to collapse
solved in the meantime?
If not, try to format /system (CARE YOU LOSE DATA) and then flash GAPPS again
http://forum.xda-developers.com/showthread.php?t=2397942
I prefer MICRO MODULAR PACKAGE or PICO MODULAR PACKAGE
Edit: Maybe only format /system could not be enought:
http://android.stackexchange.com/questions/65762/how-do-i-remove-gapps-from-cyanogenmod
(This is also for other Roms then Cyanogenmod)
Yep that's exactly what I did and the initial problem is solved
The thing was that the "system wipe" option was not in the initial tab of my recovery, I had to look around a bit (at first I was only factory reseting it, I don't really remember, but it wasn't exactly a system wipe, maybe formating the data..?)
Anyway after that everything worked fine !
IDK anything about WLAN..? But my gps is working, and I successfuly flashed BETA2 (even paraonoidandroidOTA says I'm up to date..)
So, I don't really understand why is it working ?
i need help
sKY'HER said:
Yep that's exactly what I did and the initial problem is solved
The thing was that the "system wipe" option was not in the initial tab of my recovery, I had to look around a bit (at first I was only factory reseting it, I don't really remember, but it wasn't exactly a system wipe, maybe formating the data..?)
Anyway after that everything worked fine !
IDK anything about WLAN..? But my gps is working, and I successfuly flashed BETA2 (even paraonoidandroidOTA says I'm up to date..)
So, I don't really understand why is it working ?
Click to expand...
Click to collapse
ur lucky D:
stuck at sony boot logo during first boot after installing paranoid android 4.6 beta
just installed pa 4.6 beta3 ,gapps, almost 15minutes still cellphones stuck at sony logo.
i have unlocked boot loader, rooted,installed cwm recovery i am little but worried please help me
impradeepy said:
just installed pa 4.6 beta3 ,gapps, almost 15minutes still cellphones stuck at sony logo.
i have unlocked boot loader, rooted,installed cwm recovery i am little but worried please help me
Click to expand...
Click to collapse
First boot always tooks a bit longer, but 15 min is too long i suppose...
Make a new clean flash...
wiping all data + cache + dalvik cache
Cheers mate all working after 30mins i used fastboot mode and reboot into recovery and repeated all steps once again using it from past 2hours no fc,no random reboots, gps,wireless working,screenshot fixed all good thanks paranoid android
Sent from my Xperia S using XDA Free mobile app
I have a similar issue. I tried to udpate via Paranoid OTA app from beta 3 to beta 4 (same issues on b2 => b3) and then I press install and reboot. My phone stucks at the rebooting... animation.
After Hardreset (Power + Upper-Volume button) is restarts and flashes the new rom.
Today again after clean flashing beta 4 once again stuck at Sony logo I think boot loader is not getting boot.IMG itself and after hard reset its boot up also not able to enter into cwm recovery m using dual boot Ubuntu with windows 8.1 and due to drivers issues m not able to flash the kernel img before flashing the ROM please help me
Sent from my Xperia S using XDA Free mobile app
impradeepy said:
Today again after clean flashing beta 4 once again stuck at Sony logo I think boot loader is not getting boot.IMG itself and after hard reset its boot up also not able to enter into cwm recovery m using dual boot Ubuntu with windows 8.1 and due to drivers issues m not able to flash the kernel img before flashing the ROM please help me
Sent from my Xperia S using XDA Free mobile app
Click to expand...
Click to collapse
There are more people having this problem, including me
After the new Update (BETA-4) no boot into CWM is posible
There are two suggestions:
If you can boot normaly, you can install TWRP
the second suggestion is to flash boot.img with fastboot
If you got bootloop you have to try the second one...
What problems do you have with your drivers?
There are a lot of guides how to install drivers while using Windows 8.1
stuck at sony boot logo
Targunitoth said:
There are more people having this problem, including me
After the new Update (BETA-4) no boot into CWM is posible
There are two suggestions:
If you can boot normaly, you can install TWRP
the second suggestion is to flash boot.img with fastboot
If you got bootloop you have to try the second one...
What problems do you have with your drivers?
There are a lot of guides how to install drivers while using Windows 8.1
Click to expand...
Click to collapse
after hard reset i can boot normaly...but if i reboot or shutdown then again i have to do hard reset i will install twrp now,,, i want to flash boot.img using fastboot my problem is whenever i try to connect in fastboot using windows then blue light changes into yellow means no proper connectivity with usb i do not have android sdk atm.
2. on ubuntu i can enter into fastboot blue light stable but only android tools 4.2.2 available in the repository so when ever i type fastboot reboot-bootloader then stuck on waiting device do not why this happening on linux help me
impradeepy said:
after hard reset i can boot normaly...but if i reboot or shutdown then again i have to do hard reset i will install twrp now,,, i want to flash boot.img using fastboot my problem is whenever i try to connect in fastboot using windows then blue light changes into yellow means no proper connectivity with usb i do not have android sdk atm.
2. on ubuntu i can enter into fastboot blue light stable but only android tools 4.2.2 available in the repository so when ever i type fastboot reboot-bootloader then stuck on waiting device do not why this happening on linux help me
Click to expand...
Click to collapse
You just need this one/two commands:
fastboot flash boot boot.img [ENTER]
fastboot reboot [ENTER] (optional)
take the boot.img from BETA-3
Targunitoth said:
You just need this one/two commands:
fastboot flash boot boot.img [ENTER]
fastboot reboot [ENTER] (optional)
take the boot.img from BETA-3
Click to expand...
Click to collapse
finaly i installed flashtool on ubuntu flashed boot.img saved on my hdd(extracted from pa 4.6beta4), then again clean install of rom but same error after every reboot still i have to do hard reset searching on google
impradeepy said:
finaly i installed flashtool on ubuntu flashed boot.img saved on my hdd(extracted from pa 4.6beta4), then again clean install of rom but same error after every reboot still i have to do hard reset searching on google
Click to expand...
Click to collapse
You Mean still no recovery?
The Problem is, that the CWM in PA 4.6 BETA-4 is broken.
You should extract the boot.img from BETA-3
Targunitoth said:
You Mean still no recovery?
The Problem is, that the CWM in PA 4.6 BETA-4 is broken.
You should extract the boot.img from BETA-3
Click to expand...
Click to collapse
i flashed boot.img from beta3 only one time reboot into recovery then again same problem hard reset then i can enter into using vol+ key if not then normal boot
impradeepy said:
i flashed boot.img from beta3 only one time reboot into recovery then again same problem hard reset then i can enter into using vol+ key if not then normal boot
Click to expand...
Click to collapse
Hmm, thats wired, after a clean flash boot you shouldn't get bootloop... did you wait long enough? First boot always takes a few Minutes...
You should flash boot.img from beta3,
do a clean installation of beta4
and flash boot.img from beta3 again
if you still got problems you should flash boot.img from beta3 and then install some other ROM...
Edit: to get right of your battery draining problem, you could install Pico Gapps: http://forum.xda-developers.com/showthread.php?t=2397942 without google search
Related
So i'v been trying to get cm10 on my xperia s.
I have unlocked my bootloader, and followed this guide
https://www.youtube.com/watch?v=O52IeX93Jek
Steps i took:
1.Factory reset
2.I placed the ziped "FXP221-cm-10-20130524-UNOFFICIAL-nozomi" and "gapps-jb-20121011-signed" files on the sd card
3. flashed boot.img using fast boot
4. Installed the rom and then the gaps
5. reboot
But when i reboot i'm stuck in the boot loop.
I've now tried this 3 times but always get the boot loop. What can i do to avoid that?
Just format system & then flash rom.Everything will be fine
Sent from my Xperia SL using xda premium
I'm knew to the concept of installing new roms so i need a bit more elaborate answers.
At the moment I'm back on the stock rom and would like to know what i have to do different so that i can install cm10 without getting a boot loop.
I was successful in installing a new rom.
schpongo said:
I'm knew to the concept of installing new roms so i need a bit more elaborate answers.
At the moment I'm back on the stock rom and would like to know what i have to do different so that i can install cm10 without getting a boot loop.
I was successful in installing a new rom.
Click to expand...
Click to collapse
The Reason Why You Are Getting A Bootloop.
Flashing of Boot.img is Not Proper.
What You Need To Do.
Flash boot.img using FLASHTOOL.
In the zip file you have got, extract boot.img in the zip and place it on desktop or anywhere you can find.
Keep zip file in your phone storage.
Set USB Debugging On from Settings - Developer Options.
Connect the phone to the PC.
Click 1 - Click the Lightning icon.
Select 2 - Select the Fastboot Mode.
Click 3 - Click Ok.
Click 4 - Select Reboot Into Fastboot Via Adb and wait for the phone to go into fastboot mode. (Blue led).
Click 5 - Select Reboot Into Fastboot Via Fastboot and wait for the phone to go into fastboot mode. (Blue led).
Click 6 and 7 - Select the boot.img (from desktop if you have extracted there)
Click 8 - Reboot phone. After reboot, the phone will be in recovery mode.
In Recovery
-Whip Cache Partion,
-Cache,
-Dalvik Cache,
-Fix Permissions,
Flash The ROM
(Step By Step GUIDE With Images)
http://forum.xda-developers.com/showthread.php?t=1963961
little problem
dwarkesh2492 said:
The Reason Why You Are Getting A Bootloop.
Flashing of Boot.img is Not Proper.
What You Need To Do.
Flash boot.img using FLASHTOOL.
In the zip file you have got, extract boot.img in the zip and place it on desktop or anywhere you can find.
Keep zip file in your phone storage.
Set USB Debugging On from Settings - Developer Options.
Connect the phone to the PC.
Click 1 - Click the Lightning icon.
Select 2 - Select the Fastboot Mode.
Click 3 - Click Ok.
Click 4 - Select Reboot Into Fastboot Via Adb and wait for the phone to go into fastboot mode. (Blue led).
Click 5 - Select Reboot Into Fastboot Via Fastboot and wait for the phone to go into fastboot mode. (Blue led).
Click 6 and 7 - Select the boot.img (from desktop if you have extracted there)
Click 8 - Reboot phone. After reboot, the phone will be in recovery mode.
In Recovery
-Whip Cache Partion,
-Cache,
-Dalvik Cache,
-Fix Permissions,
Flash The ROM
(Step By Step GUIDE With Images)
http://forum.xda-developers.com/showthread.php?t=1963961
Click to expand...
Click to collapse
Don't know why, but it doesn't work for me.
Got a XPeria Go with formerly CM9 on it, updated to 4.1.2 and follow this guide: http://go.apeboys.org/index-de.html wich with CM9 worked perfectly. But, now with CM10 i got everytime a Bootloop and not able to fix it.
i used also your guide for flashing the boot.img but it even doesn't work
i tried it several times, and searched for reasons and another guids and tipps, but nothing worked, and since my x10 mini got a sim-lock wich i can't fix, im a little afraid about exotic tipps.
i got an open Bootloader and everything should be ready to do this....
so my question is: How can i fix that?
thanks for help and sry for my bad english.
Exact same problem here
Aaskereija said:
Don't know why, but it doesn't work for me.
Got a XPeria Go with formerly CM9 on it, updated to 4.1.2 and follow this guide: http://go.apeboys.org/index-de.html wich with CM9 worked perfectly. But, now with CM10 i got everytime a Bootloop and not able to fix it.
i used also your guide for flashing the boot.img but it even doesn't work
i tried it several times, and searched for reasons and another guids and tipps, but nothing worked, and since my x10 mini got a sim-lock wich i can't fix, im a little afraid about exotic tipps.
i got an open Bootloader and everything should be ready to do this....
so my question is: How can i fix that?
thanks for help and sry for my bad english.
Click to expand...
Click to collapse
I don't know what's the problem here. The last thing that would cause this would be the fact that I changed the .zip's name (I did that).
AlexBurnout77 said:
I don't know what's the problem here. The last thing that would cause this would be the fact that I changed the .zip's name (I did that).
Click to expand...
Click to collapse
Thank you for the answer.
I fixed the Problem be reflashing the rom and kernel.
How?
schpongo said:
Thank you for the answer.
I fixed the Problem be reflashing the rom and kernel.
Click to expand...
Click to collapse
BTW this is still a problem for me. Nothing seems to work. I flashed everything and wiped everything before flashing but still no satisfying outcome.
Hi,
SM-P600 without ROM, without recovery, Kies and Odin doesn't work.
How can I reflash stock ROM or CM12 rom ?
Device : SM-P600 (with samsung rom stock 4.4!?)
I root my tablet with odin and teamwin 2.8.0.0 (PDA field + tar file)
the root flash should success.
I restart in recovery and install custom rom CM12 + Gapp
the tablet restart and stay to CM12 loading during all the night.
I come back into recevery mode
I try to wipe cache/dalvik => unable to mount cache/dalvik
I try to wipe cache => unable to mount cache
I try to wipe system => unable to mount system
I install Kies on my computer and try to restore the official rom with it.
The download of the rom is ok and Kies try to send the rom to the table a transfer is running during 15min (progress bar into computer windows, but no progress bar into tablet).
After that a second transfer progress bar into computer stay to 0% during 1 hour. I unplug my tablet.
Now I have got a table without recovery. I have access to download mode.
But I cannot transfer stock rom (PDA field) with Odin.
Thx for your help.
Staying at your disposal
I can flash recovery mod (TeamWin) with Odin.
But I cannot send Kies tar file by Odin.
I am downloading old stock rom (*tar) to transfer by Odin 3.09
How can I convert a CM12 zip file in tar file to tranfer it (I haven't SD card)
You could use a USB OTG cable (micro USB plug on one end and a socket like the USB ones on a computer on the other), one of these:
http://m.ebay.com.au/itm/301542874539?nav=SEARCH
And use it to plug a USB stick with the zip file on it into your tablet. You would have to mount it in twrp before flashing the zip.
They are a very useful cable to have, if your screen breaks and touch doesn't work you can use it to plug a mouse into the android device and use that for things like backing up your data before repair or disposal.
Hi I fixed the problem,
Re-Flash TWRP (many time) en try to install an unofficial KitKat version (information were write into NAND) but this version bootloop.
I wipe cache, cache/dalvik, Data, System (some eror were display in red, mount error)
I install the unofficial CM12, then the Android invite was displayed :victory:
I setup the unoficial CM12.
Reboot in recovery mode to install gapp
@Nameless One, thx for your help. In TWRP, the mount doesn't work in my case !? (It works with my Galaxy S4)
Appology for my poor English
Hi Dribounet
Dribounet said:
Hi I fixed the problem,
Re-Flash TWRP (many time) en try to install an unofficial KitKat version (information were write into NAND) but this version bootloop.
I wipe cache, cache/dalvik, Data, System (some eror were display in red, mount error)
I install the unofficial CM12, then the Android invite was displayed :victory:
I setup the unoficial CM12.
Reboot in recovery mode to install gapp
@Nameless One, thx for your help. In TWRP, the mount doesn't work in my case !? (It works with my Galaxy S4)
Appology for my poor English
Click to expand...
Click to collapse
Hi Dribounet
I have similar issue with my SM-P600.
I have tried 10 official roms , official and custom recoveries also , without success. I am absolutely sure that I am not following correctly the procedure using Odin and its version or combination of this plus wrong official ROM and so on.
Also have tried to use PIT file because I think something goes wrong with the partitions but not success again,
Would you advice with your steps you follow in order to succeed installing custom recovery.
Can I install only the recovery without ROM and how I can run in it ( button combinations)
For now I am just able to run in Download mode and with one official ROM to run the process to the middle- then goes in error with Odin and when reboot the device it shows message "Firmware upgrade encountered an issue ..... "
Thanks in advance for all answers
p600 bricked
kafencetu said:
Hi Dribounet
I have similar issue with my SM-P600.
I have tried 10 official roms , official and custom recoveries also , without success. I am absolutely sure that I am not following correctly the procedure using Odin and its version or combination of this plus wrong official ROM and so on.
Also have tried to use PIT file because I think something goes wrong with the partitions but not success again,
Would you advice with your steps you follow in order to succeed installing custom recovery.
Can I install only the recovery without ROM and how I can run in it ( button combinations)
For now I am just able to run in Download mode and with one official ROM to run the process to the middle- then goes in error with Odin and when reboot the device it shows message "Firmware upgrade encountered an issue ..... "
Thanks in advance for all answers
Click to expand...
Click to collapse
I have the same problem! There is download mode only - NO recovery, NO rom! ((
I have tried to flash original rom from sammobile via Odin. No results.
Who can help???
uno mas said:
I have the same problem! ((
Who can help???
Click to expand...
Click to collapse
Still do not have the answer and solution.I have start thinking that this is hardware issue. But when i have got it intially from the service it was able to boot in a stock bootloader and I have done something wrong with Odin and since then not able event to go in stock or custom bootloader.
Sent from my LG-D855 using Tapatalk
kafencetu said:
Still do not have the answer and solution.I have start thinking that this is hardware issue. But when i have got it intially from the service it was able to boot in a stock bootloader and I have done something wrong with Odin and since then not able event to go in stock or custom bootloader.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
In other words - should I go to the service?
uno mas said:
In other words - should I go to the service?
Click to expand...
Click to collapse
If you did not do something with it that makes the warranty not valid it is advisable to send it to service, unfortunatelly I have rooted it and they refused to accept it
Sent from my LG-D855 using Tapatalk
kafencetu said:
If you did not do something with it that makes the warranty not valid it is advisable to send it to service, unfortunatelly I have rooted it and they refused to accept it
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
SOLVED!!!
http://forum.xda-developers.com/showthread.php?t=2719750
http://forum.xda-developers.com/galaxy-note-10-2014/help/pit-stock-pit-file-thread-t2989266
uno mas said:
I have rooted also. No the warranty. But it doesn't matter if you have a bricked. ((
The Odin starts writing but no finish.
Click to expand...
Click to collapse
yep this is the case , Odin start process of writing and then suddenly - error - in the middle of the procedure.
I have tried to install only custom bootloader - pass successfully ,but then I am not able to go in bootloader mode ( I am trying with Volume down + Power , do not know is that correct - do you have an idea? )
uno mas said:
SOLVED!!!
http://forum.xda-developers.com/showthread.php?t=2719750
http://forum.xda-developers.com/galaxy-note-10-2014/help/pit-stock-pit-file-thread-t2989266
Click to expand...
Click to collapse
Hello uno mas
would you advice what tools you have used and also what order you have follow.
First update PIT and then installed the ROM or other
Thanks in advance for time and efforts!
Hey guys. I'm going crazy for days. I tried to root my T805 and something went wrong. After rooting and after the reboot there appeared many many error massages like "Google service stopped" or "android..... stopped". You can't really skip them because they are coming over and over and over. After some time it rebootes by itself and voila same issue... makes it unuseable. So right here nothing special I thought. Just flash the stock rom over it with odin and you will be fine. But whatever kind of rom or firmware I tried to flash I'm getting the same issues. Plus after every flash I got stuck at the Samsung logo incl. some vibrations in intervals. So when I get stucked (over 20 min) I have to force shutdown it and yeah it starts and hello error messages.
I rooted and flashed so many smartphones and tabs and I've never seen a problem like that. Please oh please try to help me. Probably I'll donate you some dollars for the perfect hint or solution, I'm really desperate.
Did you try wipe system before flash ROM?
Can you try install Lineage OS or wipe system and flash stock ROM
mihailrusia said:
Did you try wipe system before flash ROM?
Can you try install Lineage OS or wipe system and flash stock ROM
Click to expand...
Click to collapse
Yes. Every time I'm flashing I wipe befor and after it. And after I tried LineageOS the same happend with the error messages . But now after flashed stock ROM again it seems now that I'm totaly stuck at the Samsung logo. Even when I try to reboot and reflash I get stucked at the logo with these vibrations.
Thanks for your reply.
Ok now I'm not stucked at the logo but get the error messages again...
Are you flashing the last firmware and system and data are on ext4?
mihailrusia said:
Are you flashing the last firmware and system and data are on ext4?
Click to expand...
Click to collapse
Yes I'm flashing the latest. About the filesystem... I'm not sure. Where can I look at the filesystem? In Recovery? What I reached in the last houres: I flashed LineageOS again WITHOUT Opengapps. And boom ist startet pretty well but yea now I have no google playstore and such stuff. Now I'll try to flash the opengapps stock over the ROM using the TWPR.
Edit: I looked at the filesystem, it's ext4
You can view the partitions with DiskInfo
https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=es
Install the pico gapps
So now I flashed opengapps stock again and I'm now stucked again in at the Samsung logo. I have to hard reboot now and yeah I think there will be the error messages. But I'll try the Pico version of opengapps like you said.
Edit: I didn't have to hard reboot it. It booted by itself after some minutes but yea with the errors. After some errors it shutsdown and reboot... and so on.
If pico Gapps doesn't work install old pico Gapps. You can try with ironrom 3.2 if this doesn't work
mihailrusia said:
If pico Gapps doesn't work install old pico Gapps. You can try with ironrom 3.2 if this doesn't work
Click to expand...
Click to collapse
Pico doesn't work ... same issues. So now I'll try to flash the PhoeniX ROM v3 which is based on 5.0.2
Metero said:
Pico doesn't work ... same issues. So now I'll try to flash the PhoeniX ROM v3 which is based on 5.0.2
Click to expand...
Click to collapse
I found a post
https://forum.xda-developers.com/go...fix-install-google-gapps-stock-build-t3226205
mihailrusia said:
I found a post
https://forum.xda-developers.com/go...fix-install-google-gapps-stock-build-t3226205
Click to expand...
Click to collapse
Thanks for searching. I'll try this next. (Give me some minutes )
mihailrusia said:
I found a post
https://forum.xda-developers.com/go...fix-install-google-gapps-stock-build-t3226205
Click to expand...
Click to collapse
unfortunately it didn't work ... as long I don't flash the gapps everything is fine. I have no idea what to try next. Maybe there is a way with the ADB to do things like re-partitioning or i don't know.
Metero said:
unfortunately it didn't work ... as long I don't flash the gapps everything is fine. I have no idea what to try next. Maybe there is a way with the ADB to do things like re-partitioning or i don't know.
Click to expand...
Click to collapse
Remember to grab the right gapps that are arm but not 64 bit. Try to start fresh with any rom your're installing. Boot up tablet first before installing gapps. then reboot into recovery ( from within android hold home + vol up + vol down + power. right when tab goes black, switch finger to vol up while still holding all the other buttons. Hold until you see twrp logo). Now install your pico gapps, then reboot.
I think the important thing is to boot the system first before installing gapps. I have had to do this multiple times and have had the same issues with gapps that you're describing. Good luck and let us know how it goes.
thejase said:
Remember to grab the right gapps that are arm but not 64 bit. Try to start fresh with any rom your're installing. Boot up tablet first before installing gapps. then reboot into recovery ( from within android hold home + vol up + vol down + power. right when tab goes black, switch finger to vol up while still holding all the other buttons. Hold until you see twrp logo). Now install your pico gapps, then reboot.
I think the important thing is to boot the system first before installing gapps. I have had to do this multiple times and have had the same issues with gapps that you're describing. Good luck and let us know how it goes.
Click to expand...
Click to collapse
Thanks for your reply. I flashed every time "ARM" so not "ARM64". And the problem is that the error messages not only apply when I'm trying to flash the opengapps (when installing a ROM). The error also applys when I'm flashing the STOCK firmware with stock BL and so on... And the only ROM I was able to install was LineageOS. I also tried IronRom v3.2 but when the aroma installer finished and it rebooted there only popped up the normal Galaxy Tab S - screen... no bootloading so no Samsung - Logo ... no nothing... (and I'm really sure that I am not the problem. like I said I flashed so many ROMs and repaired so many soft bricks and I know how to follow installation instructions and that I have to wipe and to flash a new bootloader (for IronRom) etc. ... Ok so what I now try is to flash the original firmware (to reset bootloader and kernel) and then I'll try to flash the TWPR and then I do a full wipe and install LineageOS and reboot BEFORE I flash the Gapps (like you said). But honestly I don't think this will change anything.
Greets from germany
Metero said:
Thanks for your reply. I flashed every time "ARM" so not "ARM64". And the problem is that the error messages not only apply when I'm trying to flash the opengapps (when installing a ROM). The error also applys when I'm flashing the STOCK firmware with stock BL and so on... And the only ROM I was able to install was LineageOS. I also tried IronRom v3.2 but when the aroma installer finished and it rebooted there only popped up the normal Galaxy Tab S - screen... no bootloading so no Samsung - Logo ... no nothing... (and I'm really sure that I am not the problem. like I said I flashed so many ROMs and repaired so many soft bricks and I know how to follow installation instructions and that I have to wipe and to flash a new bootloader (for IronRom) etc. ... Ok so what I now try is to flash the original firmware (to reset bootloader and kernel) and then I'll try to flash the TWPR and then I do a full wipe and install LineageOS and reboot BEFORE I flash the Gapps (like you said). But honestly I don't think this will change anything.
Greets from germany
Click to expand...
Click to collapse
Try using https://forum.xda-developers.com/ga...olkit-unified-android-toolkit-galaxy-t2998205
This should take you back to stock as if the tab was new. It has many many features, including rooting the tablet for you. It runs in windows ( hopefully you have). Habben Sie einen guten Tag! (is this right? I love German but I am just learning)
EASY ROOT/UNROOT FOR S7 OR S7E ALL NOUGAT OR OREO STOCK ROMS
THANKS @klabit87 FOR OREO ROOT
TEMPORARY TWRP RECOVERY VIA ADB THANKS TO @afaneh92
This is for AT&T, T-Mobile and Verizon and Sprint running V4 bootloaders only!
This tool will allow you too easily root any stock rom allowing you to make any modifications you might want then easily unroot for better performance
This will Also give you a fully functional TWRP recovery that can be accessed via adb. TWRP is fully functional on OREO Roms but is limited on Nougat roms
The initial setup does require a data wipe.
S7 G930A Flat Odin Factory FIrmware Downloads
G930AUCU4CRI2_8.0_4File_USA (AT&T).7z
ADB_Root Temporary Twrp Tool Download
S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z
S7 G935 Edge Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G935_EDGE_OREO.7z
SM_G935_EDGE_NOUGAT.7z
S7 G930 Flat Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G930_FLAT_OREO.7z
SM_G930_FLAT_NOUGAT.7z
Instructions
1. Download S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z and your model and version you want from above
2. Unzip S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z to S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
3. Unzip the Model/Version file you downloaded and copy the files to the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and place them in the Odin folder
4. Prepare your phone for a data wipe
5. Reboot your phone to download mode and flash the AP_ROOT_G93*.tar in the Odin AP slot and reboot your phone to recovery
6. Once phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
7. Now in the cmd window make sure your device is connected and choose Option (1) Launch TWRP
8. Your phone should launch TWRP leave phone plugged in and command window open on computer
9. Now In Twrp choose wipe and choose format data. Type yes in the box when it ask
10. Now in cmd window choose Option(8) Push Root.zip to Phone
11. Now in TWRP choose install and select the Root.zip
12. After zip is installed reboot and go through setup.
13. Once through setup make sure you are rooted
To Unroot Your Phone
1. In the Root Control app choose phone settings and unroot phone make sure phone is connected to computer
2. Now depending on the type of root you choose your phone will reboot to download if you chose system root or stock recovery if you chose systemless root. If your phone reboots to download mode skip to number 5
3. If your phone reboots to recovery once your phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
4. In cmd window choose Option(3) Unroot phone will reboot too download mode
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar
To Reroot Your Phone
1. Reboot to download in Odin AP slot flash AP_ROOT_G93***.tar
2. Phone will reboot then will reboot one more time and you will be rerooted
To Enter TWRP When Rooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Manually reboot phone to recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP
2. To Exit TWRP simply choose reboot
To Enter TWRP When Unrooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Put phone in download mode In Odin AP slot flash AP_ROOT_G93***.tar force phone to reboot to recovery. If you let phone boot it will reroot and you will have to run the unroot from the root control app.
2. In recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP.
3. Do whatever you need too do
4. To exit Twrp choose reboot to Download
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
It is not possible to install Magisk, because he is installing his own boot.img and i will be stuck at bootloop? Everything is working by the way, many thanks, but i flashed Viper4Android, it doesn't work, asks for drivers all the time.
Brilliant! Many thanks as I just got this device a few days ago so the timing on this guide is perfect! I had a little trouble after I flashed the BL_ENG_BOOTLOADERS where it constantly boot-looped but once I was able to get it back into download mode (holding volume down, home button, and power button) and start again from step 5 of the unrooting process everything worked according to plan then. I'm happy to announce I've rooted, customized, and unrooted thanks to the simple ease in which this method works so many thanks to jrkruse!
SCUZZY1337 said:
It is not possible to install Magisk, because he is installing his own boot.img and i will be stuck at bootloop? Everything is working by the way, many thanks, but i flashed Viper4Android, it doesn't work, asks for drivers all the time.
Click to expand...
Click to collapse
If you just download viper4 android in xda labs store and install drivers via the app it works fine
Sent using some kind of device I modified
jrkruse said:
If you just download viper4 android in xda labs store and install drivers via the app it works fine
Sent using some kind of device I modified
Click to expand...
Click to collapse
Will try, thank you, magisk ain't work right?
---------- Post added at 07:21 PM ---------- Previous post was at 07:12 PM ----------
jrkruse said:
If you just download viper4 android in xda labs store and install drivers via the app it works fine
Sent using some kind of device I modified
Click to expand...
Click to collapse
The app is installing the driver for ages and never stops, why?
SCUZZY1337 said:
Will try, thank you, magisk ain't work right?
---------- Post added at 07:21 PM ---------- Previous post was at 07:12 PM ----------
The app is installing the driver for ages and never stops, why?
Click to expand...
Click to collapse
Reboot your phone
jrkruse said:
Reboot your phone
Click to expand...
Click to collapse
Installed thru twrp, works perfectly.
Added ATT factory firmware to the OP
jrkruse said:
Added ATT factory firmware to the OP
Click to expand...
Click to collapse
What?
SCUZZY1337 said:
What?
Click to expand...
Click to collapse
What is your what for. I didnt know adding factory firmware to OP needed an explanation
Sent using some kind of device I modified
jrkruse said:
What is your what for. I didnt know adding factory firmware to OP needed an explanation
Sent using some kind of device I modified
Click to expand...
Click to collapse
Is it possible to install magisk?
SCUZZY1337 said:
Is it possible to install magisk?
Click to expand...
Click to collapse
No it is not
Sent using some kind of device I modified
jrkruse said:
No it is not
Sent using some kind of device I modified
Click to expand...
Click to collapse
Could you please tell me the difference between V4 and V8 bootloaders?
SCUZZY1337 said:
Could you please tell me the difference between V4 and V8 bootloaders?
Click to expand...
Click to collapse
Yes v8 bootloaders means the party is over enjoy totally stock because you are not rooting or anything else unless a v8 eng boot gets released and i doubt it because v5 v6 and v7 never got released
Sent using some kind of device I modified
jrkruse said:
Yes v8 bootloaders means the party is over enjoy totally stock because you are not rooting or anything else unless a v8 eng boot gets released and i doubt it because v5 v6 and v7 never got released
Sent using some kind of device I modified
Click to expand...
Click to collapse
Idk i hav V4 and i dont have any lags, everything runs super smooth.
Bonjour,
Il est impossible de télécharger le fichier file:///C:/Users/Yves%20local/Downloads/S7_S7E_ROOT_UNROOT_ADB_TOOLS(1).7z. Le téléchargment démare et puis echec impossible de télécharger???
Merci de votre aide et bravo pour votre travail.
pyveswebsud said:
Bonjour,
Il est impossible de télécharger le fichier file:///C:/Users/Yves%20local/Downloads/S7_S7E_ROOT_UNROOT_ADB_TOOLS(1).7z. Le téléchargment démare et puis echec impossible de télécharger???
Merci de votre aide et bravo pour votre travail.
Click to expand...
Click to collapse
English is required use on xda. Please translate to English
Sent using some kind of device I modified
how compatible do you think this would be with the s7active (native to AT&T carrier) ?
especially now the S7active has recently been updated to Oreo, which also updated its bootloader to v4 ...
worth a go ?
miniminus said:
how compatible do you think this would be with the s7active (native to AT&T carrier) ?
especially now the S7active has recently been updated to Oreo, which also updated its bootloader to v4 ...
worth a go ?
Click to expand...
Click to collapse
Unless you have an eng recovery for oreo for the active and an eng boot.img for oreo you won’t be able to do anything
Sent using some kind of device I modified
Today I tried to install ArrowOS 12 on my Pixel 2 XL and it just shows the starting screen for a long time. I then tried to flash PixelExperience 12 and it starts but gets stuck at finding a Wi-Fi network. I reinstall it but apparently I did something wrong and the phone gets to boot loop and now I can only boot into boot loader.
I then try to boot a TWRP image from boot loader (I have not flashed TWRP) but I can only see the starting screen of TWRP and cannot do anything with it. I tried both twrp-3.6.0_9-0-taimen.img and twrp-3.5.2_9-0-taimen.img but get the same thing. I can use adb to get a shell command prompt though. Has anyone run into this situation?
How can I flash a ROM from here? Is there anyway I can boot a TWRP image again? Any help will be greatly appreciated.
try to flash stock rom
Type fastboot -w command and then flash twrp 5.6.0
It will work like charm
Kakashi04 said:
Type fastboot -w command and then flash twrp 5.6.0
It will work like charm
Click to expand...
Click to collapse
@Kakashi04 Appreciate your help! I am able to boot into TWRP now. Thanks!
nnSlick said:
@Kakashi04 Appreciate your help! I am able to boot into TWRP now. Thanks!
Click to expand...
Click to collapse
Glad to hear that.....
Hola, estoy en ProtonOs y quiero probar Arrow 12, ¿cómo lo hago?