I am trying to root the stock Lollipop rom of DG280 (can be find in doogee.cc)
i created custom system.img, custom recoveries, unsecured boot.img but even if i root it, it doesn't boot again.
I unpack system.img and put the su binary in xbin, then i pack it and flash , but bootloops.
Unsecured boot.img boots but when i connect phone to pc, it doesn't get recognized. I created a custom recovery based on kitkat and worked, but after installing various rooting packages, like supersu v2.46, phone boots rooted at first time, but after reboot it doesn't boot again!
Please any help appreciated.
gerstavros said:
I am trying to root the stock Lollipop rom of DG280 (can be find in doogee.cc)
i created custom system.img, custom recoveries, unsecured boot.img but even if i root it, it doesn't boot again.
I unpack system.img and put the su binary in xbin, then i pack it and flash , but bootloops.
Unsecured boot.img boots but when i connect phone to pc, it doesn't get recognized. I created a custom recovery based on kitkat and worked, but after installing various rooting packages, like supersu v2.46, phone boots rooted at first time, but after reboot it doesn't boot again!
Please any help appreciated.
Click to expand...
Click to collapse
Not sure if you have it sorted but just thought I would mention what works 100% for me. Just picked up a leo dg280 while waiting for a replacement screen for my main phone.
Anyway use kingroot to root, then google for the mrw script and follow those instructions to replace kingroot with SuperSU. So far has worked everytime for me ( have reflashed lillipop numerous times for different reasons)
Sent from my LEO_DG280 using Tapatalk
frooby said:
Not sure if you have it sorted but just thought I would mention what works 100% for me. Just picked up a leo dg280 while waiting for a replacement screen for my main phone.
Anyway use kingroot to root, then google for the mrw script and follow those instructions to replace kingroot with SuperSU. So far has worked everytime for me ( have reflashed lillipop numerous times for different reasons)
Sent from my LEO_DG280 using Tapatalk
Click to expand...
Click to collapse
I had tried that but never worked (vroot, root genius, kingroot etc). I finally flashed a custom made cwm recovery and installed a kinguser su package.
gerstavros said:
I had tried that but never worked (vroot, root genius, kingroot etc). I finally flashed a custom made cwm recovery and installed a kinguser su package.
Click to expand...
Click to collapse
What recovery did you use? I can't find any that work! Any chance you can pm me a link?
frooby said:
What recovery did you use? I can't find any that work! Any chance you can pm me a link?
Click to expand...
Click to collapse
Ι had made a custom cwm based on kitkat rom i think. It doesn't work properly in lollipop rom, it cannot read internal or external file storage partition although i was sure i had configured correctly the files, you can install a package only via adb sideload. Also it is bigger than the stock recovery and i ' m not sure if that occures any problem.
I m not sure now which file it is, if i make one for lollipop rom i ll upload it
Related
Really didn't want to make a new thread about this but honestly people just jumped to conclusions without being helpful in my previous thread.
Long story short I'm trying to manually get 4.4.2: http://forum.xda-developers.com/showthread.php?t=2664561
I saw that I needed to get s-off, which requires root. Bootloader was already unlocked and so did everything here: http://forum.xda-developers.com/showthread.php?t=2273376
I installed CWM. It said to install a superuser tool so I installed SuperSU.
"You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead." was the next line. <-- I saw that message. Installed a kernel that he recommended: http://forum.xda-developers.com/showthread.php?t=2255900
After reboot I get SuperSU error: There is no SU binary installed and SuperSU cannot install it. If you just upgraded to Android 4.3, you need to manually re-root- consult the relevant forums for your device etc.
Can anyone help me get the proper SU Binary installed? Not a beginner to rooting as I've had had several previous phones before. Never encountered something as annoying as this.
On 4.3, 3.17.502.3.
I had the same issue when I installed 4.4.2 on my international One.
What I done to root was;
- downloaded SuperSU v1.80 zip from here.
- download SuperSu from the Play Store
- in SuperSU, select the option to install binaries via TWRP/CWM. (If it doesn't reboot to recovery, manually enter recovery)
- flash the supersu v1.80 zip and reboot
- open SuperSu and install the binaries using the normal option.
That then enabled my root. I'd tried quite a few different variations and this was the only method that worked for me.
Sent from my HTC One or Note 3 via XDA Premium 4
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
mch277 said:
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
Click to expand...
Click to collapse
You seem very confused about the whole rooting process ... what was the point in flashing the stock recovery ? Are you trying to install the OTAPkg.zip ?
what Rom are you wanting to install and whats flashing stock recovery have to do with it ?
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
mch277 said:
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
Click to expand...
Click to collapse
I wrote the thread you linked too
http://forum.xda-developers.com/showthread.php?t=2659374
and yes it is necessary to have stock recovery to take an OTA, but your post didn't mention taking OTA it said you had no SU installed.
to get into stock recovery
boot to bootloader
choose recovery
wait for black screen, hold vol up and then power
you will see something about sdcard fail .. ignore it till the menu comes up
then choose to flash OTAPkg.zip from sdcard
I know that some people are having some issues working with the flash tool and downgrading their firmware to get root. There IS an easier way. The way I rooted the last time was to:
1) download one of the prerooted flashables (I chose one of the lollipop ones) and put it on my SD card,
2) use Kingroot on the .44 firmware to get temp root
3) install the dual recovery.
4) Once dual recovery installed and booted to TWRP for the first time I did a wipe (may not be necessary) and flashed the pre-rooted .zip
5) wiped cache/dalvik (again, maybe not necessary) and rebooted to rooted lollipop with supersu.
6) If kinguser is still installed (I don't believe it was for me) just uninstall it.
Do you know why after I am flashing pre-rooted.zip files, my phone stuck at Verzion boot logo forever
Can you please help?
rfresh said:
Do you know why after I am flashing pre-rooted.zip files, my phone stuck at Verzion boot logo forever
Can you please help?
Click to expand...
Click to collapse
How long is "forever"? It's been noted that it can be at the VZ screen for 15 or so minutes.
If ever in doubt, go back into TWRP, wipe everything but your internal/external storage and flash again. If that doesn't work, your prerooted .zip is likely funked up.
it won't bootup for the whole night
I fresh downloaded the same version and it still not work
Anything else I could try?
rfresh said:
Do you know why after I am flashing pre-rooted.zip files, my phone stuck at Verzion boot logo forever
Can you please help?
Click to expand...
Click to collapse
where are you getting the file from?
Over here
https://mega.nz/#!24swjQgQ!7o4tB05IEqNEC88UwE5cbESG_8hQFi7YVHZazz8h8iQ
BladeRunner said:
I know that some people are having some issues working with the flash tool and downgrading their firmware to get root. There IS an easier way. The way I rooted the last time was to:
1) download one of the prerooted flashables (I chose one of the lollipop ones) and put it on my SD card,
2) use Kingroot on the .44 firmware to get temp root
3) install the dual recovery.
4) Once dual recovery installed and booted to TWRP for the first time I did a wipe (may not be necessary) and flashed the pre-rooted .zip
5) wiped cache/dalvik (again, maybe not necessary) and rebooted to rooted lollipop with supersu.
6) If kinguser is still installed (I don't believe it was for me) just uninstall it.
Click to expand...
Click to collapse
How to install dual recovery? Anyone has a step by step guide?
Finally Kingroot worked and I'm rooted with recovery on lollipop.
I spent the day trying all the other instructions and finally looked at this thread. Got it and rooted with 5.02 installed and dual recovery. Yahoo!. I first installed 5.02 without root and was having some trouble with intermittent smartwear connectivity. Once I decided to downgrade to kitkat and root I also thought it was best to wipe the phone and am glad I did this time although reinstalling and configuring the phone will take some time. It solved my Bluetooth connection problem. Thanks for recommending kingroot. This is much easier imo. These are the procedures I used:
Using Windows 10 x64
Notes:
A: I was content with non-root 5.02 but Bluetooth connectivity was acting up with my Sony Smartband Talk.
B: Driver signing seems to be an issue with Windows 7 and 8.1 from other’s comments but not on Windows 10.
C: These procedures are for getting back to 4.4.4 from a non-rooted 5.02 phone so that root can be obtained. For just obtaining root on 4.4.4 and then upgrading to rooted 5.02, skip the first two steps.
Files and procedures:
1. Installed Flashtool 09.18.6 from here https://userscloud.com/kb6tr3bcuecr
2. From non-rooted 5.02, I used this version of Flashtool to pull the KitKat 4.4.4 version and installed to phone wiping cache, data and app settings
3. Files to install on SD card:
a. Prerooted lollipop: http://forum.xda-developers.com/z3/...ment/5-0-2-sony-xperia-z3v-prerooted-t3214182
b. Dual Recovery TWRP: Z3-lockeddualrecovery2.8.21-RELEASE.flashable.zip from: http://nut.xperia-files.com/
c. SuperUser from here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
4. Install Java SE Development Kit 8u65 Windows x64 to system from here | http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
5. Install Windows version of Kingroot from here to obtain temporary root on 4.4.4 | http://www.kingroot.net/
6. Install Dual Recovery TWRP v: Z3C-lockeddualrecovery2.8.21-RELEASE.installer.zip from here: http://nut.xperia-files.com/
Note: This version you run from Windows to obtain the first recovery after successull Kingroot and is why I installed the Java SE kit
7. Reboot phone and it comes up in recovery
8. Wipe Dalvik and Cache
9. Use the Install function in TWRP to install the Super User and Dual Recovery zip files and then the Pre-rooted lollipop. Reboot
10. Done. Old/New rooted phone. F$ck Verizon
11. Delete the flash files from SD card included in step 3 above.
Thanks and you are saying you could gain root on 5.0.2?
1, Flash 5.0.2 TFT
2, Root with Kingroot?
rfresh said:
Thanks and you are saying you could gain root on 5.0.2?
1, Flash 5.0.2 TFT
2, Root with Kingroot?
Click to expand...
Click to collapse
No, you still need to root on 4.4.x first, install dual recovery then flash the prerooted lollipop zip
BladeRunner said:
No, you still need to root on 4.4.x first, install dual recovery then flash the prerooted lollipop zip
Click to expand...
Click to collapse
Thanks, the thing is
After I install dual recovery and flash pre-rooted zip files, my phone just stay at "Verizon" logo
I struggled for nearly three weeks, still could not find a solution
Would you like to help?
rfresh said:
Thanks, the thing is
After I install dual recovery and flash pre-rooted zip files, my phone just stay at "Verizon" logo
I struggled for nearly three weeks, still could not find a solution
Would you like to help?
Click to expand...
Click to collapse
I have no idea why it won't flash. Makes no sense to me. Dumb question but you actually have the z3v for Verizon, correct, and not just a z3?
BladeRunner said:
I have no idea why it won't flash. Makes no sense to me. Dumb question but you actually have the z3v for Verizon, correct, and not just a z3?
Click to expand...
Click to collapse
yes, D6708
rfresh said:
yes, D6708
Click to expand...
Click to collapse
Just wanted to make sure. Are you flashing the zip from the internal memory or an SD card? Whichever way you are doing it try the opposite. Move it from your PC to the internal/external and flash it. It seems as if that zip is corrupted somehow. I just don't know why.
rfresh said:
Thanks and you are saying you could gain root on 5.0.2?
1, Flash 5.0.2 TFT
2, Root with Kingroot?
Click to expand...
Click to collapse
Yes, I updated my post with the procedures I used. Many thanks to all that have done the legwork in prior threads/posts.
Confused
Somebody say root 4.4.4 which I know it is already working
And you say 5.0.2, we can gain root without flash pre-rooted ROM
rfresh said:
Confused
Somebody say root 4.4.4 which I know it is already working
And you say 5.0.2, we can gain root without flash pre-rooted ROM
Click to expand...
Click to collapse
I don't know how you gain root without going back to 4.4.4 first unless I've missed something. That would have saved me a big headache.
This thread was originally for Pixel-specific rooting instructions, but by now the SuperSU ZIP and TWRP are fully supported:
- Fastboot boot TWRP
- Install latest SuperSU ZIP (v2.79-SR3 at the time of writing)
Note that at this time I recommend against fastboot flashing TWRP. With the Pixel's new partition layout, the recovery files are inside the boot partition, and so is SuperSU. If you flash both, SuperSU's internal boot image backup will not be of the original boot image, but of TWRP. This means that neither the 'full unroot' option in SuperSU, nor incremental OTA update through FlashFire, will work as expected.
OR
- Use CF-Auto-Root for Pixel (not released at the time of writing, but should be released soon)
Nice work!
Hell Yeah!!! Thanks @Chainfire, your time as well as others that have made this and the bootloader unlock happen is appreciated very much.
Sent from my Pixel XL using Tapatalk
can we flash another kernel such as elementalX on top of this?
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
How does this relate?
Ker~Man said:
How does this relate?
Click to expand...
Click to collapse
because I attempted to not really thinking about that its systemless and wasnt sure if root would persist. after attempting to flash boot elementalX's kernel my device just powered off so i immediately reflashed root and all is okay now
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
I did read the readme.. so not sure what your getting at
cwalker0906 said:
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
Click to expand...
Click to collapse
chainfire said:
- If you want to use a custom kernel, simply 'fastboot boot' the root image again after flashing the custom kernel. This has been tested with a few custom kernels and found to work well so far.
Click to expand...
Click to collapse
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
lexcyn said:
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
Click to expand...
Click to collapse
okay thanks, so i guess the answer is actually yes
Thanks @Chainfire - booted and working well!
thanks..emoji..root explorer.. viper.. naptime.. titanium.. yes..
if new kernel must boot boot to root again..
Seems I cannot remount /system_root as rw (to copy Emoji font over).
marlin://system_root/system/fonts # mount -o remount,rw /system_root
mount: '/dev/block/bootdevice/by-name/system_a'->'/system_root': Device or resource busy
Edit: Nevermind, used Solid Explorer and granted it SuperUser and seemed to work. Strange.
Does anyone have the stock boot.img for the pixel xl? I don't have the data to download the full factory image.
Life is good!
Thanks to all involved, especially Chainfire.
You Rock!
Worked like a charm. Thanks @Chainfire!
Can't thank you enough. Works perfectly.
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
spunks3 said:
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
Click to expand...
Click to collapse
fastboot boot boot-to-root.img
lexcyn said:
fastboot boot boot-to-root.img
Click to expand...
Click to collapse
what about superSU?
Hello XDA!
I am writing this thread to ask for help rooting my Samsung Galaxy J2 Pro.
I attempted to use apps such as: Framaroot, Kingroot, etc.. but so far none of them have worked and I have not been able to find a working guide on the internet of how to root my phone.
I also tried installing an unofficial version of TWRP for my phone but everytime I tried to boot into the recovery it would say "No Command" and then boot into the original recovery.
Is anyone able to help me root my phone? Can it even be done?
Any help is sincerely appreciated. Thanks!
Phone Specifications:
Samsung Galaxy J2 Pro.
SM-J250G
Android Version: 7.1.1
Bumpity Bump
Try this at your own risk
Make a backup before trying
I got root access with this method
Download stock Rom from sammobile extract and there should be 5 MD5 files extract the AP file with 7z and copied boot.img on to sdcard
Installed MagicalMmanager-7 used it to patch the boot.img to a tar file
Copied the boot image to my pc desktop then flashed the boot with odin
When I booted it back up magisk manager kept crashing so I uninstalled it and installed magiskmanager-5.23 rebooted it opened magisk and followed the prompts to update it
:good:
putzwon said:
Try this at your own risk
Make a backup before trying
I got root access with this method
Download stock Rom from sammobile extract and there should be 5 MD5 files extract the AP file with 7z and copied boot.img on to sdcard
Installed MagicalMmanager-7 used it to patch the boot.img to a tar file
Copied the boot image to my pc desktop then flashed the boot with odin
When I booted it back up magisk manager kept crashing so I uninstalled it and installed magiskmanager-5.23 rebooted it opened magisk and followed the prompts to update it
Click to expand...
Click to collapse
Hello there.
I have tried to patch my boot.img but when I put into a .tar and flash it, it doesn't flash, it's just stuck on file analysis despite being able to flash other files. Would you be able to send me a copy of your boot.img, thanks.
Kindest Regards
-Jayden
JaydenATC said:
Hello XDA!
I am writing this thread to ask for help rooting my Samsung Galaxy J2 Pro.
I attempted to use apps such as: Framaroot, Kingroot, etc.. but so far none of them have worked and I have not been able to find a working guide on the internet of how to root my phone.
I also tried installing an unofficial version of TWRP for my phone but everytime I tried to boot into the recovery it would say "No Command" and then boot into the original recovery.
Is anyone able to help me root my phone? Can it even be done?
Any help is sincerely appreciated. Thanks!
Phone Specifications:
Samsung Galaxy J2 Pro.
SM-J250G
Android Version: 7.1.1
Click to expand...
Click to collapse
Hi Jayden
I've got exactly the same problem. Have you worked this out eventually? Please help!
MC
qichen said:
Hi Jayden
I've got exactly the same problem. Have you worked this out eventually? Please help!
MC
Click to expand...
Click to collapse
Unfortunately I have not found a solution. Please notify me if you find one.
here is a copy of my boot.img after flashing this you will get a verification problem and you will have to reset your phone if it bootloops into recovery or starts to update and says no command take battery out put it back in and boot it again or boot in to odin mode and push down and boot it eventually it will boot in to recovery then factory reset it. first boot may take 5-10 minutes
my software version is J250GDXU2ARD3_J250GXSA2ARD3_XSA
putzwon said:
here is a copy of my boot.img after flashing this you will get a verification problem and you will have to reset your phone if it bootloops into recovery or starts to update and says no command take battery out put it back in and boot it again or boot in to odin mode and push down and boot it eventually it will boot in to recovery then factory reset it. first boot may take 5-10 minutes
my software version is J250GDXU2ARD3_J250GXSA2ARD3_XSA
Click to expand...
Click to collapse
Hello and thanks a lot! I flashed my boot image and now when it boots it says "Set Warranty Bit : Kernel" and an infinite booting screen.
What do I do from here? or do I need to flash the original rom?
don't worry about "Set Warranty Bit : Kernel" mine does it too here is another boot.img after i flashed this i got verification failed so i used 7z to tar userdata.img.ext4 i extracted from the AP image i got the boot.img from.
i put boot in BL and userdata in AP and flashed it. it fired up as normal and then i installed magisk apk
JaydenATC said:
Hello and thanks a lot! I flashed my boot image and now when it boots it says "Set Warranty Bit : Kernel" and an infinite booting screen.
What do I do from here? or do I need to flash the original rom?
Click to expand...
Click to collapse
Flash the original rom then flash boot and userdata as i explain in next post
Hey, sorry for the late response. Everything is working fine! I now have superuser abilities but everytime I try to flash my recovery with TWRP it just loads the stock recovery. I even tried removing certain files from the root folder to avoid the stock recovery being flashed but it hasn't worked.
Any idea? Ps. You are a life saver my man.
JaydenATC said:
Hey, sorry for the late response. Everything is working fine! I now have superuser abilities but everytime I try to flash my recovery with TWRP it just loads the stock recovery. I even tried removing certain files from the root folder to avoid the stock recovery being flashed but it hasn't worked.
Any idea? Ps. You are a life saver my man.
Click to expand...
Click to collapse
glad i could help and i don't think there is an official twrp for this device here is one i ported a couple things still don't work mtp and sideload but it's not really usable until someone ports a rom due to the data encryption which you have to format to be able to flash anything
putzwon said:
glad i could help and i don't think there is an official twrp for this device here is one i ported a couple things still don't work mtp and sideload but it's not really usable until someone ports a rom due to the data encryption which you have to format to be able to flash anything
Click to expand...
Click to collapse
Hello,
Sorry, I don't have the J250G anymore as I traded it for a J5.
Kindest Regards
Jayden
My internal storage showed I only have 8gb instead of 16gb. Is there a fix for this?
P.S. Wiping data fixes it
ok
You can extract it from the AP file from stock firmware using 7z
hey
hey everyone im just wondering but is there a kernel for this device yet or any rom ("J250G")
How to use magisk to twrp from 2.3.5 gingerbread without a computer?
@Didgeridoohan
Do you think its possible to flash twrp from a terminal emulator? Or what are my options?
If you really can't get a hold of a computer you might be lucky with an app like Franco Kernel Manager, Flashify, etc. Problem is that most apps likely won't support or be compatible with that ancient version of Android or whatever root you currently have installed. And, you're also risking bricking your device if you don't have access to a computer...
I really think your best bet is to somehow get access to a computer. Friend/school/work/something...
If you can't install stuff on that borrowed computer you could create a bootable USB with a Linux distro and run everything from there. Linux Mint is quite user friendly, they've got good documentation on how to get things running with a Live Boot USB, and it's not too hard to get adb & fastboot up and running.
Ill try and get a hold of a computer because nothing seems to work on 2.3.5
@Didgeridoohan
I had rooted using framaroot but after a factory reset it wont install supersu or superuser to my app drawer, can you give me a suggestion? Btw im using my xbox one to type this.
@chris1892006
don't waste your time with this: Magisk works only on Android 5.0 and above.
jwoegerbauer said:
@chris1892006
don't waste your time with this: Magisk works only on Android 5.0 and above.
Click to expand...
Click to collapse
thanks so do u know if its possiblle to flash a twrp.zip using terminal on 2.3.5?
chris1892006 said:
thanks so do u know if its possiblle to flash a twrp.zip using terminal on 2.3.5?
Click to expand...
Click to collapse
Is it so hard to read posts carefully?
I found this https://www.youtube.com/watch?v=-YAKGRblIuw
dd Install Method (Requires Root):
Download the latest image file (.img) from the download link above. Place it in the root of your /sdcard folder and rename it to twrp.img. Run the following commands via adb shell or a terminal emulator app:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p9
What part of the command do i change for a yp-g70 venturi? Also can i extract my twrp 2.8.0.0.zip and get the .img out of it or can i flash the .zip?
This what i used to flash cwm/ entropys daily driver kernel
https://forum.xda-developers.com/showthread.php?t=1445840
su
dd if=/sdcard/zImage of=/dev/block/mmcblk0p11
Well i got cwm installed! Now i just need to flash twrp and then a rom
chris1892006 said:
... Now i just need to flash twrp and then a rom
Click to expand...
Click to collapse
Notice, that for Lollipop and up to get it running smoothly, you need a device with minimum 2GB RAM and at least 2GHz dual core processor - what since Android 4.4+ must be a ARMv7 one.
jwoegerbauer said:
Notice, that for Lollipop and up to get it running smoothly, you need a device with minimum 2GB RAM and at least 2GHz dual core processor - what since Android 4.4+ must be a ARMv7 one.
Click to expand...
Click to collapse
Thanks i had 4.4.4 up and running but tried flashing 5.1.1 lollipop on cwm and it corrupted the bootloader. Now i cant get into recovery because twrp wouldnt flash over cwm, i tried to flash twrp 2.8.0.0 & it succeeded yet didnt work after a reboot, why? I read the op but i still cant figure out why it didnt work after a reboot? Still remained cwm.
https://forum.xda-developers.com/galaxy-player/development/recovery-twrp-v2-8-0-0-t2867742
http://www.meticulus.co.vu/p/yp-g70.html
@Didgeridoohan
How do i flash twrp over cwm?
Hey... Look at that, you had some progress. Nice.
I've never used CWM, so I wouldn't know.... Sorry.
@chris1892006
Have you backed up stock recovery IMG through e.g. Flashify app before installing a custom recovery by means of CWM ? Do remember that restoring a backup will essentially wipe any changes made after that backup.
If so then
1. you can restore or flash stock recovery IMG through Fastboot to get CWM out of your system.
2. you can install through TWRP any custom recovery IMG of your choice.
jwoegerbauer said:
@chris1892006
Have you backed up stock recovery IMG through e.g. Flashify app before installing a custom recovery by means of CWM ? Do remember that restoring a backup will essentially wipe any changes made after that backup.
If so then
1. you can restore or flash stock recovery IMG through Fastboot to get CWM out of your system.
2. you can install through TWRP any custom recovery IMG of your choice.
Click to expand...
Click to collapse
thanks only problem is they only make a .zip for twrp for my device... I don't know how to flash it.
That's a really old android version, I'm not sure if it's possible. If you don't have access to a PC, try to ask a friend if they could do it for you, just to be safe. Trying to modify stuff within android, especially on such an old version, with probably unsupported software could result in a bricked device.
Thanks but I finally got TWRP and Lollipop 5.1.1 installed it took an ADB Sideload from a PC to sideload the twrp.zip file for my device and now I'm up and running and very happy to say the very least. Sure I bricked it 3 times in the process but was always able to recover using ODIN and having the proper files on hand.
Now im having an issue with xda on the device where the xda app wont let me sign in and the browser will sign me in but go right back to the sign in page again, idk how to fix it?
I install a dalvik cache wiper with root required and it corrupted the recovery again. So I figured out the exact steps to get this device working perfectly again. Firstly the twrp folder on the external sd card has to be renamed TWRP because it has extra strange characters after the TWRP. Now we know how to restore our backup, we can start by ODIN back to stock, then Framaroot v1.4.1 root the device then download entropys daily driver kernel cwm, the flash it via terminal emulator, reboot, then you have to install meticulous carbon 4.4.4 to fix the partitions and update the cwm to adb sideload the twrp. So you can then flash Meticulus Carbon 5.1.1 and both updates and 5.1.1 pico gapps. Good to go. Meticulus made the kernel overclock to 1.7ghz and it runs pretty darn good honestly. I modded the build.prop vm dalvik heap limit to 384m from 128m to get some extra performance out of it.