Recovery Testing SM-T330NU CLOSED - Galaxy Tab 4 General

OKay, so
the thread for our working Philz/Advanced CWM recovery for the sm-t330nu is located here;
http://forum.xda-developers.com/tab-4/development/recovery-philz-smnu-t2980094
more work to do but will need to wait till i have the device.
-------------------------------------
NOTE- @gr8nole has opened TWRP recovery thread in development
http://forum.xda-developers.com/tab-4/development/twrp-2-8-2-0-unofficial-t330-t2980716
--------------------------------------
This thread will be closed as it has served it's purpose. Thanks everyone ! =)

I'm a wus and don't want to test but thank you for helping move this device forward. Looking forward to some good news here.

xnatex21 said:
I'm a wus and don't want to test but thank you for helping move this device forward. Looking forward to some good news here.
Click to expand...
Click to collapse
x,
hi,
no worries, i completely understand. as it happens i may be recieving an sm-t330nu by way of donation sometime soon
specifically for the purpose of developing. This call is meant for those with experience. I will say i am working towards
putting together device trees for sm-t33x in general just in case.
be good
m

I considered looking into a recovery build for this device. But, based on the lack of responses to this thread, I don't see enough interest to make it a worthwhile endeavor. I see several threads asking for a recovery, but no responses when someone builds a test???

gr8nole said:
I considered looking into a recovery build for this device. But, based on the lack of responses to this thread, I don't see enough interest to make it a worthwhile endeavor. I see several threads asking for a recovery, but no responses when someone builds a test???
Click to expand...
Click to collapse
I got this device just yesterday, Big improvement from the T210R for sure. Of course we all want a recovery but don't want to risk our tabs

gr8nole said:
I considered looking into a recovery build for this device. But, based on the lack of responses to this thread, I don't see enough interest to make it a worthwhile endeavor. I see several threads asking for a recovery, but no responses when someone builds a test???
Click to expand...
Click to collapse
Yeah, it's a little meh. But mainly i'm working on getting my tree for this tab sorted
while i wait for it to arrive. Maybe the OP is a little harsh. ... meh.
:silly:
m

Rusell said:
I got this device just yesterday, Big improvement from the T210R for sure. Of course we all want a recovery but don't want to risk our tabs
Click to expand...
Click to collapse
No risk, no reward.

moonbutt74 said:
No risk, no reward.
Click to expand...
Click to collapse
Especially since it is a new device...
What could go wrong?? What is the worst thing that could happen??

Flashing a bad recovery is not really even a risk. I probably flashed 50 bad recoveries when trying to get the T210 recoveries working. As long as you have stock recovery image to re-flash (Odin) there really isn't any risk.

gr8nole said:
Flashing a bad recovery is not really even a risk. I probably flashed 50 bad recoveries when trying to get the T210 recoveries working. As long as you have stock recovery image to re-flash (Odin) there really isn't any risk.
Click to expand...
Click to collapse
Does the Firmware from sammobile .com for SM-T330NU contain stock recovery?

Rusell said:
Does the Firmware from sammobile .com for SM-T330NU contain stock recovery?
Click to expand...
Click to collapse
It should, but MB has it posted in the OP also. :good:

Rusell said:
Does the Firmware from sammobile .com for SM-T330NU contain stock recovery?
Click to expand...
Click to collapse
The stock recovery is linked to in OP
Rusell,
I mean this in the best way,
You may not meet the requirements I set out in OP
for a tester. Which is nothing bad. If you're willing to wait, I should be receiving my tab
this coming week, at which time I won't need a tester . My effort is geared toward getting
things moving.
m

Well i flashed and it just keeps rebooting over and over trying to get into recovery, Here is what is read at the top left corner every time:
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
It wont let me go further then just seeing the "Samsung galaxy Tab 4" splash screen.

Rusell said:
Well i flashed and it just keeps rebooting over and over trying to get into recovery, Here is what is read at the top left corner every time:
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
It wont let me go further then just seeing the "Samsung galaxy Tab 4" splash screen.
Click to expand...
Click to collapse
Okay, connect via adb and see if you can get logcat,
the hang means the kernel is good, but the fstab may be wrong, or i need to patch init and adb.
thanks,
m

moonbutt74 said:
Okay, connect via adb and see if you can get logcat,
the hang means the kernel is good, but the fstab may be wrong, or i need to patch init and adb.
thanks,
m
Click to expand...
Click to collapse
give me ambitmto get to my comp, if you're willing to run another test pm me please.

moonbutt74 said:
give me ambitmto get to my comp, if you're willing to run another test pm me please.
Click to expand...
Click to collapse
So how do i take logcat from adb and when should i do it,While flashing or while booting?
Excuse me since im a newb

Rusell said:
So how do i take logcat from adb and when should i do it,While flashing or while booting?
Excuse me since im a newb
Click to expand...
Click to collapse
Oops , okay skip that, okay this test is a fail you can refurn to stock and delete the custom,
i will mark test 1 as fail and take it down.
m

Rusell,
okay, round 2 if you're up for it,
ROUND 2 http://d-h.st/8U5f -modified default.prop,fstab temp test with prebuilt kernel and dt.img
the kernel should be msm8226, if this fails i will revisit my config and run a new build,
m

and if you are really feeling frisky, give this TWRP a try.
http://d-h.st/Qm3

gr8nole said:
and if you are really feeling frisky, give this TWRP a try.
http://d-h.st/Qm3
Click to expand...
Click to collapse
hey, if you're jumping in cool, how do i add you as contributor ?
m

Related

djrbliss releases AT&T S4 bootloader vuln.

I was wondering now that djrbliss has released the vulnerability for AT&T SGS4 do we have to wait for devs to do something with it? For Loki tools it seems as if you have to have a recovery already made. Will a current one work?
https://github.com/djrbliss/loki
this seems more like a user made htc dev, not what true s-off "bootloader unlocked" would be. non the less it should work fine. this probably wont touch the write enabled protection on the device. the only issues i see is until we are truly unlocked we will always have that "samsung custom" on out bootscreens.
spyz88 said:
I was wondering now that djrbliss has released the vulnerability for AT&T SGS4 do we have to wait for devs to do something with it? For Loki tools it seems as if you have to have a recovery already made. Will a current one work?
https://github.com/djrbliss/loki
Click to expand...
Click to collapse
He released his source code and such so we need to have someone compile it into a .bat or .exe so we can flash a custom recovery/rom
its linux only, and devs need to use/make teh loki_patch.
someone could make a windows/android app to interface with loki_flash for end users though...
shabbypenguin said:
its linux only, and devs need to use/make teh loki_patch.
someone could make a windows/android app to interface with loki_flash for end users though...
Click to expand...
Click to collapse
well i cant use it as i don't use linux lol.
Everyone - if you don't know what to do with those files without asking, don't try it yourself. There's already one in process in the development thread, and there will be cleaner and simpler ones out within just a few hours, I'm sure - with complete instructions.
Until you can nandroid the phone, this is not something to screw around with
fix-this! said:
well i cant use it as i don't use linux lol.
Click to expand...
Click to collapse
well if you dont use linux you cant make kernels or recoveries
luckily the loki_flash utility that is used to actually put the patched img onto the device works on android so it doenst matter what kind of computer you have
alacrify said:
Everyone - if you don't know what to do with those files without asking, don't try it yourself. There's already one in process in the development thread, and there will be cleaner and simpler ones out within just a few hours, I'm sure - with complete instructions.
Until you can nandroid the phone, this is not something to screw around with
Click to expand...
Click to collapse
A mod should put that up as a temp announcement in these forums. Seriously. Can't wait for the noobs to start crying in the Q&A area.... haha.
just means soon we will have bootloader unlocked.... patience
lorijuan1024 said:
just means soon we will have bootloader unlocked.... patience
Click to expand...
Click to collapse
i thought that's what this tool did. maybe this is why adam is still working on a bootloader unlock thats permanent. this should tide us over though.
Bjray said:
A mod should put that up as a temp announcement in these forums. Seriously. Can't wait for the noobs to start crying in the Q&A area.... haha.
Click to expand...
Click to collapse
Exactly, I have one phone booting to recovery now, no issues. YET! better know what you are doing, or you will have a serious paperweight.
I re-booted out of successful, so will see.
Update: nand backup was successful. Good start for us, just need the perm fix, but for now, it rocks, it was so nice to see the recovery screen. SWEET
TheAxman said:
Exactly, I have one phone booting to recovery now, no issues. YET! better know what you are doing, or you will have a serious paperweight.
I re-booted out of successful, so will see.
Click to expand...
Click to collapse
im not going to try the method yet, at least for a few days. i also see alot of soft bricked devices tonight.
fix-this! said:
i thought that's what this tool did. maybe this is why adam is still working on a bootloader unlock thats permanent. this should tide us over though.
Click to expand...
Click to collapse
what i meant was a tool that us people that aren't good with the programming language can use.
fix-this! said:
im not going to try the method yet, at least for a few days. i also see alot of soft bricked devices tonight.
Click to expand...
Click to collapse
Agreed, but I do have a jtag box here in hand, and there is no fix for that either, I might have one phone down soon..:
Incoming update from Samsung in 3....2....1.....
I flashed what shabbypenguin provided in his recovery thread and now have a working recovery on my ATT i337!!! :laugh::good::highfive::fingers-crossed:
Thanks to djrbliss for his awesome work!
mr_blanket said:
Incoming update from Samsung in 3....2....1.....
Click to expand...
Click to collapse
simple solution is to not take the OTA. but yes, i see one coming to.
fix-this! said:
simple solution is to not take the OTA. but yes, i see one coming to.
Click to expand...
Click to collapse
Yes, everyone needs to keep the OTA .apk's frozen from now on. Or use a custom rom that doesn't have them.
mattdm said:
Yes, everyone needs to keep the OTA .apk's frozen from now on. Or use a custom rom that doesn't have them.
Click to expand...
Click to collapse
hopefully adam can get us a more permanent solution. but props to dan for his tool.
Couldn't be happier after I get home from watching the hangover I get to unlock this bad boy
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

[Q] TWRP and encrypted storage

I just updated to Lollipop. I tried to run TWRP without flashing (use fastboot boot command) and it run smoothly. However, after I encrypted my phone TWRP cannot decrypt the storage like it could in Kitkat even though I enabled encryption in Kikkat too
nerodarknight said:
TWRP cannot decrypt the storage like it could in Kitkat
Click to expand...
Click to collapse
Correct.
rootSU said:
Correct.
Click to expand...
Click to collapse
So no worry then, I thought it's only my phone lol. Do you happen to know if TWRP or CWM will make it compatible with Lollipop encryption?
nerodarknight said:
So no worry then, I thought it's only my phone lol. Do you happen to know if TWRP or CWM will make it compatible with Lollipop encryption?
Click to expand...
Click to collapse
Forget CWM, it doesn't even support encryption for KK.
Anybody know how long it has taken the devs of TWRP to update to the new encryption for previous versions? Just curious about when this will work again.
Thanks for any info,
Fly
FlyOnTheWall43 said:
Anybody know how long it has taken the devs of TWRP to update to the new encryption for previous versions? Just curious about when this will work again.
Thanks for any info,
Fly
Click to expand...
Click to collapse
It will come when it comes.
Lethargy said:
Forget CWM, it doesn't even support encryption for KK.
Click to expand...
Click to collapse
Forget encryption, It doesn't even support /sdcard for JB!
Lethargy said:
It will come when it comes.
Click to expand...
Click to collapse
Is it just me or are these responses the least productive thing on the internet?
I would understand if I came in here demanding an exact ETA, but I feel like I respectfully asked for estimated past turn around times so that I could have a basic idea (2 weeks/2 months/2 years) of when I'll be able to use TWRP on my phone again.
And I understand that the devs are probably working very hard on getting this done (I see that there is version 2.8.2 for the Nexus 9 that allows decryption on Lollipop, so maybe they're really close), and although I am an entry level programmer, this kind of stuff goes way over my head, I do really appreciate the work that they do.
I am fairly new to the wonderful world of this level of Android customization and I'm just trying to learn how the process works.
Does anybody else have any useful info?
FlyOnTheWall43 said:
Is it just me or are these responses the least productive thing on the internet?
I would understand if I came in here demanding an exact ETA, but I feel like I respectfully asked for estimated past turn around times so that I could have a basic idea (2 weeks/2 months/2 years) of when I'll be able to use TWRP on my phone again.
And I understand that the devs are probably working very hard on getting this done (I see that there is version 2.8.2 for the Nexus 9 that allows decryption on Lollipop, so maybe they're really close), and although I am an entry level programmer, this kind of stuff goes way over my head, I do really appreciate the work that they do.
I am fairly new to the wonderful world of this level of Android customization and I'm just trying to learn how the process works.
Does anybody else have any useful info?
Click to expand...
Click to collapse
There isn't anything else to say other than what I did in the post. Check repos and see if there is any progress.
But still.
As mentioned, we don't know anything. We haven't had any feedback. You have access to the same info we do (TWRP dev thread and github). There is no point asking us the answer. You'd be more upset if no one answered at all.
Again, I wasn't asking for when the next version will be released, I understand nobody knows that... I asked for:
FlyOnTheWall43 said:
for estimated past turn around times so that I could have a basic idea (2 weeks/2 months/2 years)
Click to expand...
Click to collapse
Just a rough guess, that's all I'm wondering.
FlyOnTheWall43 said:
Again, I wasn't asking for when the next version will be released, I understand nobody knows that... I asked for:
Just a rough guess, that's all I'm wondering.
Click to expand...
Click to collapse
Without knowing the complexities of encryption and the development involved and the fact that past development turn around has nothing to do with the future, we can give only the same answer.
I'd say you can only ask the dev, but since that's against the rules, you'll just have to wait and find out when everyone else does. You have the same information available as we have, including past turn around dates.
New 2.8.2.0 with Android 5 encryption support is available at the TWRP site and confirmed working on my Nexus 5

[ROM] Galaxy Light Testers wanted

evening all,
im looking for users with the galaxy light (t399 or t399n) who would be willing to help test some new roms and kernels and be part of helping develop builds from the ground up for the light, i do not have a galaxy light (and im not likely to get one over in the UK) buit i do have a similar but slightly higher specced device (galasy s5 mini) so i am trying to also dev for the light but i need some willing volunteers who dont mind trying out builds that may not work at first and who are able to try and get adb logs so i can fix errors etc.
anyone interested, would be starting with a 5.1.1 rom then moving on to 6.0 (cm13 probably) once 5.1 is usable
reply to this thread or drop me a pm if your interested
I've got a t399 I use as a backup device now, be glad to help out when I can.
Nevermindthelabel said:
I've got a t399 I use as a backup device now, be glad to help out when I can.
Click to expand...
Click to collapse
well ive got a test build ready to go wen you have time
DJ_Steve said:
well ive got a test build ready to go wen you have time
Click to expand...
Click to collapse
Just plugged it in a few minutes ago. If you want to pm me or post a link I'll give it a shot
Nevermindthelabel said:
Just plugged it in a few minutes ago. If you want to pm me or post a link I'll give it a shot
Click to expand...
Click to collapse
link pm'd to you
Have a SGH-T399N. Willing to test custom firmware as long as it doesn't totally screw over the device. lol
DJ_Steve said:
link pm'd to you
Click to expand...
Click to collapse
Tried it a few times, can't get it to flash in twrp. Have 2.8.4 on the phone, it would just fail then tried flashing your 3.0 but that does not stay on for more than 30 seconds. Even turned the timeout off
Nevermindthelabel said:
Tried it a few times, can't get it to flash in twrp. Have 2.8.4 on the phone, it would just fail then tried flashing your 3.0 but that does not stay on for more than 30 seconds. Even turned the timeout off
Click to expand...
Click to collapse
What error does flash give
Sent from my SM-G800F using Tapatalk
DJ_Steve said:
What error does flash give
Sent from my SM-G800F using Tapatalk
Click to expand...
Click to collapse
ApplyParsedPerms: lsetfilecon of /system/lost+found to u object_r:system_file:s0 failed Operation not supported on transport endpoint set_metadata_recursive: some changes failed E:error executing updater binary in zip
Sorry took me so long to get back to you
Nevermindthelabel said:
ApplyParsedPerms: lsetfilecon of /system/lost+found to u object_r:system_file:s0 failed Operation not supported on transport endpoint set_metadata_recursive: some changes failed E:error executing updater binary in zip
Sorry took me so long to get back to you
Click to expand...
Click to collapse
ok ill do a rebuild to try fix that later
Nevermindthelabel said:
ApplyParsedPerms: lsetfilecon of /system/lost+found to u object_r:system_file:s0 failed Operation not supported on transport endpoint set_metadata_recursive: some changes failed E:error executing updater binary in zip
Sorry took me so long to get back to you
Click to expand...
Click to collapse
ok another build to test out : ive had some pc problems last few days so sorry for delay
http://www.dmpwap.xyz/testing/light/pac_gardalte_LP-MR1.Unofficial_20160227-113134.zip
DJ_Steve said:
ok another build to test out : ive had some pc problems last few days so sorry for delay
http://www.dmpwap.xyz/testing/light/pac_gardalte_LP-MR1.Unofficial_20160227-113134.zip
Click to expand...
Click to collapse
Awww pac rom deffo testing this so glad to see this here thought you was having a crack at cm first.
DJ_Steve said:
ok another build to test out : ive had some pc problems last few days so sorry for delay
http://www.dmpwap.xyz/testing/light/pac_gardalte_LP-MR1.Unofficial_20160227-113134.zip
Click to expand...
Click to collapse
This time for me it flashed but it was super quick. Like 5 seconds. When I went to reboot system twrp said no operating system installed. Hate to be the bearer of bad news once again
DJBoxer said:
Awww pac rom deffo testing this[emoji14]so glad to see this here thought you was having a crack at cm first.
Click to expand...
Click to collapse
I have pac build env setup already as am building it for s5mini. Will probs do cm13 at some point tho.
Sent from my SM-G800F using Tapatalk
Nevermindthelabel said:
This time for me it flashed but it was super quick. Like 5 seconds. When I went to reboot system twrp said no operating system installed. Hate to be the bearer of bad news once again
Click to expand...
Click to collapse
well that didnt flash properly lol,
try these odin images :
http://www.dmpwap.xyz/testing/light/gardalte.zip
flash those in odin and see what happens
DJ_Steve said:
ok another build to test out : ive had some pc problems last few days so sorry for delay
http://www.dmpwap.xyz/testing/light/pac_gardalte_LP-MR1.Unofficial_20160227-113134.zip
Click to expand...
Click to collapse
Yeah i had same flashed within 5 seconds and going to reboot system leads to no os installed :laugh::silly:
DJ_Steve said:
try these odin images :
http://www.dmpwap.xyz/testing/light/gardalte.zip
flash those in odin and see what happens
Click to expand...
Click to collapse
Tried this by odin left me at powered by android splash screen.
Was unable to pull any logcats guessing device doesent even get deamon started?.
checked recovery log nothing special mentioned there other then i pulled log to ext sd lol
sorry not much help on this one maybe some one else may have more info.
DJBoxer said:
Tried this by odin left me at powered by android splash screen.
Was unable to pull any logcats guessing device doesent even get deamon started?.
checked recovery log nothing special mentioned there other then i pulled log to ext sd lol[emoji14]sorry not much help on this one maybe some one else may have more info.
Click to expand...
Click to collapse
I probably need to mod the boot image to start adb only as if it sits at powered by Android I'll bet it's complaining about shared libs
Sent from my GT-I9505 using Tapatalk
DJ_Steve said:
I probably need to mod the boot image to start adb only as if it sits at powered by Android I'll bet it's complaining about shared libs
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Well i look forward to next update then not really much to go on as i know you dont have device to hand and without and info its basically like taking a pissing in a tea cup in the dark lol once im able to grab those logs sure it be more helpfull least it didnt brick hahaha:good:
p.s your on the s4 today :cyclops: lol
DJBoxer said:
Well i look forward to next update then not really much to go on as i know you dont have device to hand and without and info its basically like taking a pissing in a tea cup in the dark lol once im able to grab those logs sure it be more helpfull least it didnt brick hahaha:good:
p.s your on the s4 today :cyclops: lol
Click to expand...
Click to collapse
S4 lte lol. Yea been playing with aicp on s5m. It's very difficult toto truly brick a Samsung unless your an idiot haha.
Sent from my GT-I9505 using Tapatalk
DJBoxer said:
Well i look forward to next update then not really much to go on as i know you dont have device to hand and without and info its basically like taking a pissing in a tea cup in the dark lol once im able to grab those logs sure it be more helpfull least it didnt brick hahaha:good:
p.s your on the s4 today :cyclops: lol
Click to expand...
Click to collapse
okay
new images to try
http://www.dmpwap.xyz/testing/light/boot.img
http://www.dmpwap.xyz/testing/light/system.img
http://www.dmpwap.xyz/testing/light/pac_gardalte_LP-MR1.Unofficial_20160229-111259.zip

FNF Ifive Mini 4S root?

Hello xda,
I recently bought the newly released FNF Ifive Mini 4S from Banggood and i was wondering if anyone is planning to make a root and/or custom recovery for it?
Thanks
+1
Me too, I own one of the beauties, and I would love to have it rooted!
fdomi said:
+1
Me too, I own one of the beauties, and I would love to have it rooted!
Click to expand...
Click to collapse
What are your experiences so far?
I just bought one for about 85€.
Hope it gets a little more attention and someone can root it.
Where? Can't find it for that price.
Hello, Can owners of this tablet give me some info on it's thermal performance? Specifically, how warm the case gets on the hands, CPU temps under load and the SoCs throttling behavior.
Thanks.
lost2 said:
Where? Can't find it for that price.
Click to expand...
Click to collapse
It was an offer/sale on Gearbest!
However it wasnt shipped even after 2 weeks... china :fingers-crossed:
R. D. said:
Hello, Can owners of this tablet give me some info on it's thermal performance? Specifically, how warm the case gets on the hands, CPU temps under load and the SoCs throttling behavior.
Thanks.
Click to expand...
Click to collapse
Will do if i get my hands on mine! Will do some stress tests and see how warm it gets!
I ordered it too for 100$ on gearbest. Finally after week and a half it is shipped out now, but tracking still shows pre-advised, so I think I won't get it for at least 2-3 weeks
Ordered mine from gearbest a couple days ago so it will be a while before I get it. I have rooted and installed custom firmwares on other tablets before so I have a basic understanding of how things work but I have never done this totally from scratch. I have been doing a lot of research and study on this and have a few ideas. First thing I'm going to try is to boot a custom recovery for the rk2388 chip with the fastboot boot recovery.img command and then then do some backups of the nand. After that I will try to extract the kernel from stock and insert it into a generic android 6.01 rom and see if I can flash it from within the custom recovery. Hopefully it will work( I know I will have to work on drivers and such too) but first things first just want to see if it will work. My main thing I'm scared of is messing it up and bricking the tablet. I'm hoping that providing fastbooting the custom recovery works I can restore to stock ROM if I mess anything up. Wish me luck and let me know if you have any ideas that may help.
+1 interested in this tablet.
Απουσιολόγος said:
For root, try "Kingroot ".
Click to expand...
Click to collapse
Have you tested it?
In this specific device no, but it worked in all devices I own.
When you get it, give KingoRoot a try. Chances are it will work.. Hopefully..
Joeblah said:
Ordered mine from gearbest a couple days ago so it will be a while before I get it. I have rooted and installed custom firmwares on other tablets before so I have a basic understanding of how things work but I have never done this totally from scratch. I have been doing a lot of research and study on this and have a few ideas. First thing I'm going to try is to boot a custom recovery for the rk2388 chip with the fastboot boot recovery.img command and then then do some backups of the nand. After that I will try to extract the kernel from stock and insert it into a generic android 6.01 rom and see if I can flash it from within the custom recovery. Hopefully it will work( I know I will have to work on drivers and such too) but first things first just want to see if it will work. My main thing I'm scared of is messing it up and bricking the tablet. I'm hoping that providing fastbooting the custom recovery works I can restore to stock ROM if I mess anything up. Wish me luck and let me know if you have any ideas that may help.
Click to expand...
Click to collapse
If you brick it FNF has a recovery tool themselves. It is an update/recovery tool and can be found by googleing: fnf ifive mini 4s upgrade tool. Just pick the first one from techtablets.com.
There seems to be TWRP available for similar RK3288 Tablets here: http://crewrktablets.arctablet.com/?p=4776
It's a bit of an old post though, only TWRP 2.8.4.0, not sure if it will work 100% on this device. Would love to know if it works.
stephendt0 said:
There seems to be TWRP available for similar RK3288 Tablets here: http://crewrktablets.arctablet.com/?p=4776
It's a bit of an old post though, only TWRP 2.8.4.0, not sure if it will work 100% on this device. Would love to know if it works.
Click to expand...
Click to collapse
I found this post as well yesterday and decided to test it. TWRP does not seem to work, but CWM works just fine! I successfully installed chainfires supersu. Should I write a small tutorial or something?
UnknownDK said:
I found this post as well yesterday and decided to test it. TWRP does not seem to work, but CWM works just fine! I successfully installed chainfires supersu. Should I write a small tutorial or something?
Click to expand...
Click to collapse
Yes please!
stephendt0 said:
Yes please!
Click to expand...
Click to collapse
Will get right to it then!
stephendt0 said:
Yes please!
Click to expand...
Click to collapse
It is done You can find it here
Today is shaping up to be a great day. First I wake up and receive notice stating that my tablet has finally shipped. Then I come here and see more activity on this forum with progress. Congrats and good job on installing chanfires SuperSU DK. Does that mean you have full root now? And also did you install cwm or use the fastboot boot recovery recovery.img command just to boot the recovery?

Needing rom flashing advice

The phone is not fully booting.
What?
aholeinthewor1d said:
What?
Click to expand...
Click to collapse
Just because my Verizon pixel ran into a boot loop after Resurrection rom a change grom purenexus. I've known issues from the past to be about build, ( European, ECT.) Or order of operations. Even supersu, usually after the fact for supersu. As a junior member with some xp I started this thread anyway after an Odin to stock. What did I do wrong,? Google pixel, Verizon, NOF26V, unlocked. I flashed twice, then Odin. Still looped.
April fool's ... ? Odin ... Really
piperx said:
April fool's ... ? Odin ... Really
Click to expand...
Click to collapse
I was thinking the same thing
Right so... I wanted to flash Resurrection rom. I did that with TWRP duh. And pixel won't finish it's boot for 30plus minutes after. So what do I do? I Odin stock NOF26V in download mode to get my phone running again. Comprehend?
piperx said:
April fool's ... ? Odin ... Really
Click to expand...
Click to collapse
Yeah, Odin. Download mode. That's how to save a phone from a bad rom flash
alladinscastle said:
Yeah, Odin. Download mode. That's how to save a phone from a bad rom flash
Click to expand...
Click to collapse
Odin is a Samsung thing. Fastboot mode or recovery or bootloader mode are the usual terms for a Google phone.
alladinscastle said:
Right so... I wanted to flash Resurrection rom. I did that with TWRP duh. And pixel won't finish it's boot for 30plus minutes after. So what do I do? I Odin stock NOF26V in download mode to get my phone running again. Comprehend?
Click to expand...
Click to collapse
I comprehend just fine, the real question though:
Do you have any idea what your doing ?
piperx said:
I comprehend just fine, the real question though:
Do you have any idea what your doing ?
Click to expand...
Click to collapse
I had no problems flashing pureexus on my Verizon pixel. Resurrection rom is giving me problems. Phone won't boot past Google screen. Matched vendor. It's not that. What Android build is Resurrection Rom based on?
alladinscastle said:
I had no problems flashing pureexus on my Verizon pixel. Resurrection rom is giving me problems. Phone won't boot past Google screen. Matched vendor. It's not that. What Android build is Resurrection Rom based on?
Click to expand...
Click to collapse
Really?
https://forum.xda-developers.com/pixel-xl/development/rom-t3548615
If im running 7.1.1 and Resurrection is 7.1.0. could the downgrade from flashing cause my problem?
alladinscastle said:
If im running 7.1.1 and Resurrection is 7.1.0. could the downgrade from flashing cause my problem?
Click to expand...
Click to collapse
wipe your data and cache partitions.
alladinscastle said:
I had no problems flashing pureexus on my Verizon pixel. Resurrection rom is giving me problems. Phone won't boot past Google screen. Matched vendor. It's not that. What Android build is Resurrection Rom based on?
Click to expand...
Click to collapse
How in the hell do people flash things they know nothing about?
Do you read at least the op of anything you flash?
I'm still tryin to get over the Odin post
Answer this. Resurrection's thread title says 7.1.1. The Op says 7.1.0r7. " users are now asking if the new build will be 7.1.2. " What is is the current build based on. If the Op is outdated, what good is it?
P.s. I have seen some op updates on the rom thread... ok, some things are still outdated.
Your attitude needs work, maybe consider not replying. I do know some things about rom flashing. It is unnecessary to be rude. It is ok to make corrections about a post.
piperx said:
How in the hell do people flash things they know nothing about?
Do you read at least the op of anything you flash?
I'm still tryin to get over the Odin post
Click to expand...
Click to collapse
Do you enjoy showing off? At be more class at it.......
alladinscastle said:
Do you enjoy showing off? At be more class at it.......
Click to expand...
Click to collapse
Just because I do my homework (read, read some more, read again, read til I fully understand) before I blindly install something is not showing off.
It's called "common sense"
This stuff is not rocket science
piperx said:
Just because I do my homework (read, read some more, read again, read til I fully understand) before I blindly install something is not showing off.
It's called "common sense"
This stuff is not rocket science
Click to expand...
Click to collapse
I agree on this. I do the same, read, read, and read some more until I understand what I am doing. I used to root phones that aren't "google" versions and learned how much of a pain it was.. therefore I am owned the last Nexus brand, and the first Pixel. Using a Google phone is so much easier! But yeah, reading is key. I hopped into this thread to see if someone needed some help, read through the posts, and was so lost as to what this user is doing.. Odin? If the user who is having issues is reading this, just boot your phone to bootloader, use fastboot and format userdata the device (wipe/format) and then fastboot flash the stock 7.1.2 image and wait for custom ROMs to update.
piperx said:
Just because I do my homework (read, read some more, read again, read til I fully understand) before I blindly install something is not showing off.
It's called "common sense"
This stuff is not rocket science
Click to expand...
Click to collapse
Alright moving on. Just generic crap on my thread here
Great news. I'm am now running Resurrection ROM. All I did differently for my Verizon pixel was move from 26V to 27B build. I flashed the rom and twrpRC1, Then I rebooted to bootloader mode and flashed the vender using the adb fastboot command. "Fastboot flash vendor vendor.img" need more specific instruction. See me!!! No more problems here.

Categories

Resources